CVE-2026-57573

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.6Exploit: 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 and scraper. Prior to 0.9.0, the Docker API server applied its SSRF destination check on the non-streaming /crawl path but not on the streaming path. handle_stream_crawl_request passed seed URLs straight to the crawler with no destination validation, allowing a remote unauthenticated client to call POST /crawl/stream or POST /crawl with crawler_config.stream=true with a URL pointing at an internal, private, or link-local address; the server fetched it and streamed the response body back. This issue is fixed in version 0.9.0.

CVSS v3
8.6
EG Score
8.6(medium)
EPSS
17.7%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (1)

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

Unauthenticated SSRF on the Docker server streaming crawl path (/crawl/stream) · Advisory · unclecode/crawl4ai · GitHub

https://github.com/unclecode/crawl4ai/security/advisories/GHSA-wm69-2pc3-rmmf

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
crawl4ai0.3.0 ... 0.8.9 (67 versions)0.9.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 30× 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-14 02:24 UTCEG score recompute
  2. 2026-07-13 22:31 UTCEPSS rescore
  3. 2026-07-13 15:34 UTCEG score recompute
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 04:43 UTCEG score recompute
  7. 2026-07-12 17:52 UTCEG score recompute
  8. 2026-07-12 07:00 UTCEG score recompute
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 20:09 UTCEG score recompute
  11. 2026-07-11 09:18 UTCEG score recompute
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-10 22:27 UTCEG score recompute
  15. 2026-07-10 11:26 UTCEG score recompute
  16. 2026-07-10 00:34 UTCEG score recompute
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 13:41 UTCEG score recompute
  20. 2026-07-09 02:51 UTCEG score recompute
  21. 2026-07-08 16:00 UTCEG score recompute
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-08 05:09 UTCEG score recompute
  25. 2026-07-07 18:16 UTCEG score recompute
Show 5 more
  1. 2026-07-07 13:46 UTCEPSS rescore
  2. 2026-07-07 13:46 UTCEPSS rescore
  3. 2026-07-07 07:23 UTCEG score recompute
  4. 2026-07-06 20:30 UTCEG score recompute
  5. 2026-07-06 20:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57573?
CVE-2026-57573 is a high vulnerability published on July 6, 2026. Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server applied its SSRF destination check on the non-streaming /crawl path but not on the streaming path. handlestreamcrawlrequest passed seed URLs straight to the crawler with no destination validation,…
When was CVE-2026-57573 disclosed?
CVE-2026-57573 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57573 actively exploited?
CVE-2026-57573 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57573?
CVE-2026-57573 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-57573?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57573, 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-57573

Explore →

Is Your Infrastructure Affected by CVE-2026-57573?

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

Start Free Scan →Browse All CVEs