CVE-2026-57573: high-severity vulnerability in unclecode crawl4ai
Crawl4AI unauthenticated SSRF in Docker streaming crawl endpoint
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.6epss 0.4%
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:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Affected products
unclecode · crawl4aiRelated CVEs — unclecode crawl4ai
In the same product, most dangerous first.
CVE-2026-53753CRITICALCrawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker APIEPSS 2.9%CVE-2026-53755HIGHCrawl4AI: SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF checkEPSS 1.6%CVE-2026-57572CRITICALCrawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_argsEPSS 0.9%CVE-2026-57571CRITICALCrawl4AI arbitrary file write via download filename path traversalEPSS 0.8%CVE-2026-91941HIGHCrawl4AI before 0.9.3 Denial of Service via PDFContentScrapingStrategyEPSS 0.5%CVE-2026-91940HIGHcrawl4ai before 0.9.3 Arbitrary File Write via PDFContentScrapingStrategyEPSS 0.5%