Skip to content
OpenAdvisories
High · 8.6 Scanner template CVE-2026-53755 EUVD-2026-38567GHSA-6qhc-x826-342cPYSEC-2026-588

Crawl4AI: SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check

Published Jun 23, 2026 · Updated Jun 26, 2026 · Assigned by GitHub_M

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.

Affected products

VendorProductAffectedFixed
unclecode crawl4ai < 0.8.9 —

Automated scanner template

A ready-made Nuclei template detects this vulnerability automatically. Vulnerabilities with public scanner templates are typically probed across the internet soon after the template appears — exposed systems should be patched first.

Source: projectdiscovery/nuclei-templates (MIT) — updated daily. Only links are listed.

Affected packages

EcosystemPackageAffectedFixedRecord
PyPI crawl4ai < 0.8.9 0.8.9 GHSA-6qhc-x826-342c

References