CVE-2026-56266 Crawl4AI - Server-Side Request Forgery via Direct Crawl Endpoints
Unauthenticated attackers can exploit SSRF in Crawl4AI to access internal services and cloud metadata by bypassing blocklists with IPv6-mapped IPv4 addresses.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-56266?
CVE-2026-56266 is a critical server-side request forgery vulnerability in Crawl4AI, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Crawl4AI before 0.8.7 contains a server-side request forgery vulnerability in the /crawl, /crawl/stream, /md, and /llm endpoints that fetch arbitrary user-supplied URLs without validation. Unauthenticated attackers can bypass the internal-address blocklist using IPv6-mapped IPv4 addresses to reach internal services and cloud metadata endpoints.
Weakness: CWE-918
Which versions are affected by CVE-2026-56266?
It affects 1 product.
Products include Kidocode Crawl4ai.
How do I fix CVE-2026-56266?
Upgrade to a fixed version.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-56266 being exploited?
There is no known exploitation of CVE-2026-56266 in the wild and no public exploit code.
Other vulnerabilities in Crawl4AI
- CVE-2026-57572 Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args
- CVE-2026-26216 Crawl4AI < 0.8.0 Docker API Unauthenticated Remote Code Execution via Hooks Parameter
- CVE-2026-53753 Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API
- CVE-2026-57571 Crawl4AI arbitrary file write via download filename path traversal
- CVE-2026-56265 Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key