CVE-2026-53755

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Crawl4AI is an open-source LLM friendly web crawler & scraper. Prior to 0.8.9, the Docker API server applied its SSRF destination check to the crawl target URL only, not to the proxy address. An unauthenticated request could supply a proxy pointing at an internal IP and route the browser through it, reaching internal services and cloud-metadata endpoints, while using a perfectly valid crawl URL. The Docker API is unauthenticated by default. /crawl, /crawl/stream, and /crawl/job accept a browser_config (and crawler_config). The following all feed Chromium's egress and were unchecked: browser_config.proxy_config.server, browser_config.proxy (deprecated field), crawler_config.proxy_config.server, and --proxy-server / --proxy-pac-url / --proxy-bypass-list / --host-resolver-rules flags in browser_config.extra_args. This vulnerability is fixed in 0.8.9.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
20.7%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check · Advisory · unclecode/crawl4ai · GitHub

https://github.com/unclecode/crawl4ai/security/advisories/GHSA-6qhc-x826-342c

Vendor Advisories for CVE-2026-53755(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)
PackageVulnerable rangeFixed inDependents
crawl4ai0.3.0 ... 0.8.8 (66 versions)0.8.9—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 54× 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.

  1. 2026-07-06 22:58 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 23:33 UTCEG score recompute
  7. 2026-07-05 10:42 UTCEG score recompute
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 21:51 UTCEG score recompute
  11. 2026-07-04 09:01 UTCEG score recompute
  12. 2026-07-03 13:45 UTCEG score recompute
  13. 2026-07-03 00:21 UTCEG score recompute
  14. 2026-07-02 11:31 UTCEG score recompute
  15. 2026-07-01 22:38 UTCEG score recompute
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-07-01 09:03 UTCEG score recompute
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 20:12 UTCEG score recompute
  20. 2026-06-30 07:21 UTCEG score recompute
  21. 2026-06-29 18:31 UTCEG score recompute▼ 1.10
  22. 2026-06-29 17:26 UTCNVD updateCVSS v3 → 7.5
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 05:41 UTCEG score recompute
Show 29 more
  1. 2026-06-28 16:38 UTCEG score recompute
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 03:48 UTCEG score recompute
  6. 2026-06-27 14:58 UTCEG score recompute
  7. 2026-06-27 03:08 UTCEPSS rescore
  8. 2026-06-27 02:07 UTCEG score recompute
  9. 2026-06-26 13:17 UTCEG score recompute
  10. 2026-06-26 00:25 UTCEG score recompute
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-25 11:27 UTCEG score recompute
  13. 2026-06-24 22:37 UTCEG score recompute
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-24 09:47 UTCEG score recompute
  16. 2026-06-23 20:53 UTCEG score recompute
  17. 2026-06-23 08:01 UTCEG score recompute
  18. 2026-06-22 19:07 UTCEG score recompute
  19. 2026-06-22 06:13 UTCEG score recompute
  20. 2026-06-21 17:17 UTCEG score recompute
  21. 2026-06-21 04:10 UTCEG score recompute
  22. 2026-06-20 15:07 UTCEG score recompute
  23. 2026-06-20 02:15 UTCEG score recompute
  24. 2026-06-19 13:21 UTCEG score recompute
  25. 2026-06-19 00:30 UTCEG score recompute
  26. 2026-06-18 11:39 UTCEG score recompute
  27. 2026-06-17 22:46 UTCEG score recompute
  28. 2026-06-17 09:56 UTCEG score recompute
  29. 2026-06-16 21:06 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-53755?
CVE-2026-53755 is a high vulnerability published on June 16, 2026. Crawl4AI is an open-source LLM friendly web crawler & scraper. Prior to 0.8.9, the Docker API server applied its SSRF destination check to the crawl target URL only, not to the proxy address. An unauthenticated request could supply a proxy pointing at an internal IP and route the browser through…
When was CVE-2026-53755 disclosed?
CVE-2026-53755 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53755 actively exploited?
CVE-2026-53755 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53755?
CVE-2026-53755 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-53755?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53755, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53755

Explore →

Is Your Infrastructure Affected by CVE-2026-53755?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs