Quick answers
- Is CVE-2026-56261 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56261 being exploited in the wild.
- How severe is CVE-2026-56261?
- High severity, with a CVSS score of 8.6, published 10 July 2026.
- Which products and versions are affected?
- Crawl4AI Crawl4AI < 0.8.7.
- Is there a fix for CVE-2026-56261?
- A patch was published on 2026-07-10: Version 0.8.7 released with fixes Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56261 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-56261?
- 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 Docker API server within the /crawl/job and /llm/job endpoints. These endpoints accept user-supplied webhook URLs but fail to validate the destination address. An unauthenticated remote attacker can provide URLs pointing to internal IP ranges (RFC 1918), loopback addresses, or cloud metadata services (e.g., 169.254.169.254). This allows the attacker to probe internal network services or exfiltrate sensitive environment metadata. The issue is fixed in version 0.8.7 by implementing a blocklist for private and metadata IP ranges and hostnames, and disabling redirect following for webhooks.
Affected products
- Crawl4AI Crawl4AI < 0.8.7
Timeline
- 2026-06-02: advisory: Vendor security advisory published on GitHub
- 2026-07-10: disclosed: CVE published to NVD
- 2026-07-10: patched: Version 0.8.7 released with fixes