Quick answers
- Is CVE-2026-56264 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56264 being exploited in the wild.
- How severe is CVE-2026-56264?
- High severity, with a CVSS score of 8.1, published 30 June 2026.
- Which products and versions are affected?
- Crawl4AI Crawl4AI < 0.8.7.
- Is there a fix for CVE-2026-56264?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-56264 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-56264?
- 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 code injection vulnerability (CWE-94) exists in the /execute_js endpoint of the Crawl4AI Docker API server. The endpoint accepts and executes user-supplied JavaScript in the server's browser context. Because the browser is launched with the '--disable-web-security' flag enabled by default, an attacker can bypass the Same-Origin Policy (SOP). This allows for arbitrary JavaScript execution and Server-Side Request Forgery (SSRF) against internal services and cloud metadata endpoints. The vulnerability is addressed in version 0.8.7 by disabling the endpoint by default, removing the insecure browser flag, and implementing a destination URL blocklist.
Affected products
- Crawl4AI Crawl4AI < 0.8.7
Timeline
- 2026-06-02: advisory: Vendor security advisory published (GHSA-365w-hqf6-vxfg)
- 2026-06-30: disclosed: CVE-2026-56264 published to NVD