Crawl4AI
Crawl4AI: SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check
Crawl4AI is an open-source LLM friendly web crawler & scraper. Prior to 0.8.9, the Docker API server applied its SSRF destination check to the crawl target URL only, not to the proxy address. An unauthenticated request could supply a proxy pointing at an internal IP and route the browser through it, reaching internal services and cloud-metadata endpoints, while using a perfectly valid crawl URL. The Docker API is unauthenticated by default. /crawl, /crawl/stream, and /crawl/job accept a browser_config (and crawler_config). The following all feed Chromium's egress and were unchecked: browser_config.proxy_config.server, browser_config.proxy (deprecated field), crawler_config.proxy_config.server, and --proxy-server / --proxy-pac-url / --proxy-bypass-list / --host-resolver-rules flags in browser_config.extra_args. This vulnerability is fixed in 0.8.9.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.8.9
Fixed in 0.8.9
Mitigation
Upgrade crawl4ai to 0.8.9 or later.
References
- Vendor advisory github.com/unclecode/crawl4ai/security/advisor…
Timeline
Days relative to CVE publicationFirst public PoC 44 days after publication; not in CISA KEV. First PoC: nuclei template: crawl4ai < 0.8.9 - Server Side Request Forgery (nuclei template, 6 Aug 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: crawl4ai < 0.8.9 - Server Side Request Forgery | 6 Aug 2026 | 14 Nov 2026 |