# CVE-2026-56266: unclecode Crawl4AI SSRF in crawl and extraction endpoints

Source: https://junglewise.ai/threats/cve-2026-56266-unclecode-crawl4ai-ssrf-in-crawl-and-extraction-endpoints  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-22. Updated: 2026-06-22  
License: CC BY 4.0 with a link back

CVE-2026-56266 · Severity: high · CVSS 8.6 · Published 2026-06-22

Crawl4AI, an open-source tool used to crawl and scrape web content for Large Language Models (LLMs), contains a security flaw in its web-facing endpoints. An attacker can use the tool to make unauthorized requests to internal company servers or cloud management services that are normally hidden from the internet. This could lead to the exposure of sensitive internal data, cloud credentials, or configuration details.

## Quick answers

**Is CVE-2026-56266 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-56266 being exploited in the wild.

**How severe is CVE-2026-56266?** High severity, with a CVSS score of 8.6, published 22 June 2026.

**Which products and versions are affected?** unclecode Crawl4AI < 0.8.7.

**Is there a fix for CVE-2026-56266?** A patch was published on 2026-06-22: Fix released in version 0.8.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-56266 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-56266?** Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in Crawl4AI's primary crawl endpoints (/crawl, /crawl/stream, /md, and /llm) due to insufficient validation of user-supplied URLs. While the application implements a blocklist for internal addresses, attackers can bypass these protections using IPv6-mapped IPv4 addresses (e.g., [::ffff:169.254.169.254]). This allows unauthenticated remote attackers to force the server to fetch data from internal network resources, Docker networks, or cloud metadata services (IMDS). The issue is resolved in version 0.8.7, which introduces normalized URL validation and a more robust blocklist check.

## Affected products

- unclecode Crawl4AI < 0.8.7

## Timeline

- 2026-06-02: advisory: Vendor security advisory published (GHSA-365w-hqf6-vxfg)
- 2026-06-22: disclosed: CVE-2026-56266 published to NVD
- 2026-06-22: patched: Fix released in version 0.8.7

## References

- [https://github.com/unclecode/crawl4ai](https://github.com/unclecode/crawl4ai)
- [https://github.com/unclecode/crawl4ai/security/advisories/GHSA-365w-hqf6-vxfg](https://github.com/unclecode/crawl4ai/security/advisories/GHSA-365w-hqf6-vxfg)
- [https://www.vulncheck.com/advisories/crawl4ai-server-side-request-forgery-via-direct-crawl-endpoints](https://www.vulncheck.com/advisories/crawl4ai-server-side-request-forgery-via-direct-crawl-endpoints)