CVE-2026-53755
Crawl4AI is an open-source LLM friendly web crawler & scraper. …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/unclecode/crawl4ai/security/advisories/GHSA-6qhc-x826-342c
- github.com/advisories/GHSA-6qhc-x826-342c
- nvd.nist.gov/vuln/detail/CVE-2026-53755
- github.com/pypa/advisory-database/tree/main/vulns/crawl4ai/PYSEC-2026-588.yaml
- nvd.nist.gov/vuln/detail/CVE-2026-53755
- cve.org/CVERecord?id=CVE-2026-53755
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.