CVE-2026-53755
HighCrawl4AI: SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check
Published Jun 16, 2026 · Updated Aug 12, 2026 · Also known as GHSA-6qhc-x826-342c, PYSEC-2026-588
Key Facts
Patch in the next maintenance window- CVE-2026-53755 is a high-severity vulnerability (CVSS 7.5 v3.1) affecting Crawl4ai (Kidocode).
- It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
- EPSS estimates a 1.6% probability of exploitation in the next 30 days.
- Fixed versions are available, including Crawl4ai 0.8.9.
- Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.
CVSS v3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (30-day exploit likelihood)
1.6%
Higher than 75.0% of all scored CVEs
Exploited in the wild
No known
Not in a known-exploited catalog
Public exploit code
None known
Get the full CVE-2026-53755 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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
3 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Crawl4aiKidocode | >= < 0.8.9 | 0.8.9 |
Patched Releases
Crawl4ai
0.8.9
Timeline
Publicly disclosed
Jun 16, 2026
Last updated
Aug 12, 2026
Weakness Type
- CWE-918 Server-Side Request Forgery (SSRF)
References
- advisoryGHSA advisory
- advisoryhttps://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53755.json
- advisoryhttps://github.com/pypa/advisory-database/tree/main/vulns/crawl4ai/PYSEC-2026-588.yaml
- advisoryhttps://github.com/unclecode/crawl4ai/security/advisories/GHSA-6qhc-x826-342c
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-53755
FAQ
Common Questions.
Crawl4AI is an open-source LLM friendly web crawler & scraper.
Affected: Crawl4ai (Kidocode) versions >= < 0.8.9. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Crawl4ai 0.8.9.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.
Is CVE-2026-53755 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo