Vulnerability Description
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 Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Kidocode | Crawl4Ai | < 0.9.0 |
Related Weaknesses (CWE)
References
- https://github.com/unclecode/crawl4ai/commit/60886d1a0c52682e4c83a7cef9dfac417ffPatch
- https://github.com/unclecode/crawl4ai/security/advisories/GHSA-wm69-2pc3-rmmfMitigationVendor Advisory
FAQ
What is CVE-2026-57573?
CVE-2026-57573 is a vulnerability with a CVSS score of 8.6 (HIGH). 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...
How severe is CVE-2026-57573?
CVE-2026-57573 has been rated HIGH with a CVSS base score of 8.6/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-57573?
Check the references section above for vendor advisories and patch information. Affected products include: Kidocode Crawl4Ai.