Crawl4AI is an open-source LLM friendly web crawler & scraper. Prior to 0.8.8, the Docker API server's SSRF protection (validate_webhook_url / validate_url_destination in deploy/docker/utils.py) used an explicit IPv4/IPv6 CIDR blocklist that missed several address families. An attacker could reach internal services and cloud metadata endpoints (e.g. 169.254.169.254) despite the filter by encoding an internal IPv4 address inside an IPv6 transition form, or by using the IPv6 unspecified address. Because the Docker API is unauthenticated by default (jwt_enabled: false), no credentials are required. This vulnerability is fixed in 0.8.8.
CVE-2026-53754
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 18.3%
- KEV
- Not listed
Published
June 16, 2026
Last Modified
June 29, 2026
Advisory Details (1)
Auto-updated Jun 23, 2026SSRF filter bypass in Docker server via IPv6 transition forms (NAT64 / 6to4 / unspecified / v4-mapped) · Advisory · unclecode/crawl4ai · GitHub
https://github.com/unclecode/crawl4ai/security/advisories/GHSA-4qqr-vv2q-cmr5Vendor Advisories for CVE-2026-53754(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| crawl4ai | 0.3.0 ... 0.8.7 (65 versions) | 0.8.8 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 55× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 22:58 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 23:49 UTCEG score recompute
- 2026-07-05 10:54 UTCEG score recompute
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 21:57 UTCEG score recompute
- 2026-07-04 09:02 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 15:21 UTCEG score recompute
- 2026-07-03 02:23 UTCEG score recompute
- 2026-07-02 13:27 UTCEG score recompute
- 2026-07-02 00:32 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 11:30 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 22:35 UTCEG score recompute
- 2026-06-30 09:36 UTCEG score recompute
- 2026-06-29 20:40 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
Show 30 moreShow fewer
- 2026-06-29 07:45 UTCEG score recompute
- 2026-06-28 18:48 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 05:52 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 16:50 UTCEG score recompute
- 2026-06-27 03:54 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 14:59 UTCEG score recompute
- 2026-06-26 02:03 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:07 UTCEG score recompute
- 2026-06-25 00:11 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 11:11 UTCEG score recompute
- 2026-06-23 22:13 UTCEG score recompute
- 2026-06-23 09:02 UTCEG score recompute
- 2026-06-22 20:06 UTCEG score recompute
- 2026-06-22 07:08 UTCEG score recompute
- 2026-06-21 17:53 UTCEG score recompute
- 2026-06-21 04:40 UTCEG score recompute
- 2026-06-20 15:43 UTCEG score recompute
- 2026-06-20 02:48 UTCEG score recompute
- 2026-06-19 13:52 UTCEG score recompute
- 2026-06-19 00:55 UTCEG score recompute
- 2026-06-18 11:57 UTCEG score recompute
- 2026-06-17 22:59 UTCEG score recompute
- 2026-06-17 10:03 UTCEG score recompute
- 2026-06-16 21:06 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-53754?
When was CVE-2026-53754 disclosed?
Is CVE-2026-53754 actively exploited?
What is the CVSS score of CVE-2026-53754?
How do I remediate CVE-2026-53754?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53754
Is Your Infrastructure Affected by CVE-2026-53754?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.