{"document":{"category":"csaf_vex","csaf_version":"2.0","title":"CVE-2026-53755: Crawl4AI: SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check","publisher":{"category":"vendor","name":"HarborGuard Database","namespace":"https://database.harborguard.co"},"tracking":{"id":"CVE-2026-53755","status":"final","version":"1","initial_release_date":"2026-06-23T18:15:31.586Z","current_release_date":"2026-06-23T18:15:31.586Z","revision_history":[{"date":"2026-06-23T18:15:31.586Z","number":"1","summary":"Initial machine-readable export from HarborGuard."}]},"distribution":{"tlp":{"label":"WHITE"},"text":"Public CVE data; freely redistributable."},"notes":[{"category":"description","text":"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.","title":"CVE description"}],"references":[{"category":"self","summary":"CVE-2026-53755 on HarborGuard Database","url":"https://database.harborguard.co/cve/CVE-2026-53755"},{"category":"external","summary":"CVE Record","url":"https://www.cve.org/CVERecord?id=CVE-2026-53755"},{"category":"external","summary":"https://github.com/unclecode/crawl4ai/security/advisories/GHSA-6qhc-x826-342c","url":"https://github.com/unclecode/crawl4ai/security/advisories/GHSA-6qhc-x826-342c"}]},"product_tree":{"branches":[{"category":"vendor","name":"unclecode","branches":[{"category":"product_name","name":"crawl4ai","branches":[{"category":"product_version","name":"< 0.8.9","product":{"name":"unclecode crawl4ai < 0.8.9","product_id":"CSAFPID-1","product_identification_helper":{"cpe":"cpe:2.3:a:unclecode:crawl4ai:\\<_0.8.9:*:*:*:*:*:*:*"}}}]}]}]},"vulnerabilities":[{"cve":"CVE-2026-53755","title":"Crawl4AI: SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check","notes":[{"category":"description","text":"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.","title":"CVE description"}],"product_status":{"known_affected":["CSAFPID-1"]},"scores":[{"cvss_v3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","baseScore":8.6,"baseSeverity":"HIGH"},"products":["CSAFPID-1"]}],"remediations":[{"category":"none_available","details":"No fixed version is published yet. Monitor the upstream advisory.","product_ids":["CSAFPID-1"]}]}]}