CVE-2026-53755
- Source
- https://cve.org/CVERecord?id=CVE-2026-53755
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53755.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-53755
- Aliases
- Published
- 2026-06-23T18:15:31.586Z
- Modified
- 2026-07-08T08:13:44.015399344Z
- Severity
-
- 8.6 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N CVSS Calculator
- Summary
- Crawl4AI: SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check
- Details
-
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 browserconfig (and crawlerconfig). The following all feed Chromium's egress and were unchecked: browserconfig.proxyconfig.server, browserconfig.proxy (deprecated field), crawlerconfig.proxyconfig.server, and --proxy-server / --proxy-pac-url / --proxy-bypass-list / --host-resolver-rules flags in browserconfig.extra_args. This vulnerability is fixed in 0.8.9.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53755.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-918" ] }- References
Affected packages
Git / github.com/unclecode/crawl4ai
Affected ranges
- Type
- GIT
- Repo
- https://github.com/unclecode/crawl4ai
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed
- Database specific
{ "source": [ "AFFECTED_FIELD", "CPE_RANGE" ], "cpe": "cpe:2.3:a:kidocode:crawl4ai:*:*:*:*:*:*:*:*", "extracted_events": [ { "introduced": "0" }, { "fixed": "0.8.9" } ] }