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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/unclecode/crawl4ai/commit/60886d1a0c52682e4c83a7cef9dfac417fff6bd2 Patch
- https://github.com/unclecode/crawl4ai/security/advisories/GHSA-wm69-2pc3-rmmf Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.6 · kidocodeNVD modified 2026-10-25 20:10
Affected (CPE criteria) 1
cpe:2.3:a:kidocode:crawl4ai:*:*:*:*:*:*:*:*