Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Kidocode | Crawl4Ai | < 0.8.9 |
Related Weaknesses (CWE)
References
- https://github.com/unclecode/crawl4ai/security/advisories/GHSA-6qhc-x826-342cThird Party Advisory
FAQ
What is CVE-2026-53755?
CVE-2026-53755 is a vulnerability with a CVSS score of 8.6 (HIGH). 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 unaut...
How severe is CVE-2026-53755?
CVE-2026-53755 has been rated HIGH with a CVSS base score of 8.6/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-53755?
Check the references section above for vendor advisories and patch information. Affected products include: Kidocode Crawl4Ai.