Crawl4AI: SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-918 and the CVSS impact.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| unclecode | crawl4ai | before 0.8.9 | 0.8.9 | Patch available | CNA |
| — | crawl4ai (PyPI) | before 0.8.9 | 0.8.9 | Patch available | GHSA-6qhc-x826-342c |
- crawl4ai Vendorunclecode Affected before 0.8.9 Fixed in 0.8.9 Patch available CNA
- crawl4ai (PyPI) Vendor— Affected before 0.8.9 Fixed in 0.8.9 Patch available GHSA-6qhc-x826-342c
Remediation
- Fix · CNA crawl4ai (unclecode) Fixed in 0.8.9
- Fix · GHSA-6qhc-x826-342c crawl4ai (PyPI) Fixed in 0.8.9 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-53755
- 2026-10-03 Alias added: GHSA-6qhc-x826-342c
References
More unclecode Crawl4ai vulnerabilities
- TI-2026-38760 Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API CVSS 3.1CRITICAL 10.0
- TI-2026-40630 Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key CVSS 4.0CRITICAL 9.3
- TI-2026-21207 Crawl4AI < 0.8.0 Docker API Unauthenticated Remote Code Execution via Hooks Parameter CVSS 4.0CRITICAL 10.0
- TI-2026-41423 Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args CVSS 3.1CRITICAL 10.0
- TI-2026-21208 Crawl4AI < 0.8.0 Docker API Local File Inclusion via file URL Handling CVSS 4.0CRITICAL 9.2
- TI-2026-40631 Crawl4AI - Server-Side Request Forgery via Direct Crawl Endpoints CVSS 4.0CRITICAL 9.2
Sources
- CVE-2026-53755 · CVE Program
- CVE-2026-53755 · NVD
- FIRST EPSS
- GHSA-6qhc-x826-342c · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences