{“lastseen”:””,”description”:”Crawl4AI is an open-source LLM friendly web crawler \\u0026 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.”,”published”:”2026-06-23T18:15:31.586Z”,”modified”:”2026-06-23T18:15:31.586Z”,”type”:”cve”,”title”:”Crawl4AI: SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check”,”source”:”GitHub_M”,”references”:”https:\/\/github.com\/unclecode\/crawl4ai\/security\/advisories\/GHSA-6qhc-x826-342c”,”id”:”CVE-2026-53755″,”bulletinFamily”:””,”cwe”:[“CWE-918″],”cvelist”:null,”sourceData”:”unclecode crawl4ai \\u003c 0.8.9″,”sourceHref”:””,”cvss”:{“score”:8.6,”severity”:”HIGH”,”vector”:”CVSS:3.1\/AV:N\/AC:L\/PR:N\/UI:N\/S:C\/C:H\/I:N\/A:N”,”version”:”3.1″},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:””,”category_name”:”CVE”,”post_link”:””,”product”:”crawl4ai”,”version”:”\\u003c 0.8.9″,”vendor”:”unclecode”,”ai_description”:”SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check”,”ai_severity”:”High”,”ai_vendor”:”unclecode”,”ai_product”:”Crawl4AI”,”ai_version”:”\\u003c 0.8.9″,”ai_score”:8.6}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:””,”description”:”Crawl4AI is an open-source LLM friendly web crawler \\u0026 scraper. Prior to 0.8.9, the Docker API server applied its SSRF destination check to the crawl…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[6,8,81,12,15,13,7,11,5],"class_list":["post-65220","post","type-post","status-publish","format-standard","hentry","category-category_cve","tag-cve","tag-cvss","tag-cvss-86","tag-exploit","tag-high","tag-news","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n