Crawl4AI from 0.8.7 through 0.9.5 contains a server-side request forgery vulnerability in the Docker API server that allows unauthenticated attackers to bypass destination checks via URL userinfo parsing differences. Attackers can set fetch_ssl_certificate=true with crafted userinfo URLs so SSLCertificate.from_url connects to internal hosts on port 443, probing reachability and leaking certificate details.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- StatusReceived → DeferredNVD modified 2026-10-19 21:14
- First seenCVSS 6.9NVD modified 2026-10-19 17:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/unclecode/crawl4ai/blob/v0.9.5/crawl4ai/async_crawler_strategy.py
- https://github.com/unclecode/crawl4ai/blob/v0.9.5/crawl4ai/ssl_certificate.py
- https://github.com/unclecode/crawl4ai/blob/v0.9.5/deploy/docker/utils.py
- https://github.com/unclecode/crawl4ai/pull/2304
- https://www.vulncheck.com/advisories/crawl4ai-0.8.7-through-0.9.5-ssrf-bypass-via-sslcertificate-from-url-url-userinfo