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.
Affected products
kidocode: crawl4ai
References2
- github.com/unclecode/crawl4ai/security/advisories/GHSA-wm69-2pc… MitigationVendor Advisory
- github.com/unclecode/crawl4ai/commit/60886d1a0c52682e4c83a7cef9… Patch
Metrics
- CVSS 3.1
-
8.6
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N - EPSS — exploit probability
- 0% percentile: 39 · as of 15 November 2026
- CWE
- CWE-918
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.