CVE-2026-57573: Crawl4AI unauthenticated SSRF in Docker streaming crawl endpoint
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, allowing a remote unauthenticated client to call POST /crawl/stream or POST /crawl with crawlerconfig.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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Crawl4AI Docker streaming crawl endpointto a version that resolves this vulnerability.Fixed in 0.9.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-57573?
CVE-2026-57573 has a severity rating of 8.6, classified as high.
How do I fix CVE-2026-57573?
To fix CVE-2026-57573, upgrade your Crawl4AI software to version 0.9.0 or later.
What type of vulnerability is CVE-2026-57573?
CVE-2026-57573 is an unauthenticated Server-Side Request Forgery (SSRF) vulnerability.
What component of Crawl4AI is affected by CVE-2026-57573?
CVE-2026-57573 affects the Docker streaming crawl endpoint in Crawl4AI.
Can CVE-2026-57573 lead to unauthorized access?
Yes, CVE-2026-57573 can potentially allow attackers to exploit the Docker API through SSRF, leading to unauthorized access.