Quick answers
- Is CVE-2026-115508 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115508 being exploited in the wild.
- How severe is CVE-2026-115508?
- Medium severity, with a CVSS score of 6.5, published 22 October 2026.
- Which products and versions are affected?
- Unclecode Crawl4AI 0.7.0 before 0.9.5.
- Is there a fix for CVE-2026-115508?
- Yes: fixed in 0.9.5. Until then: Restrict network access to the Crawl4AI Docker API server to only trusted clients that require web crawling functionality. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115508 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-115508?
- Check whether you run Unclecode Crawl4AI at an affected version. 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.
How to fix
- Fixed in: 0.9.5
Restrict network access to the Crawl4AI Docker API server to only trusted clients that require web crawling functionality.
Technical details
The vulnerability exists in RegexExtractionStrategy.custom, RegexChunking.patterns, and schema regex fields (JsonCss, JsonXPath, JsonLxml) which accept caller-supplied regex patterns from API request bodies without validation. An attacker authenticated to the Docker API can submit catastrophic-backtracking regex patterns that cause Python's re engine to hang while holding the GIL, preventing the crawl deadline mechanism from interrupting execution. The fix refuses untrusted regex patterns from API bodies, allowing only built-in patterns.
Affected products
- unclecode Crawl4AI 0.7.0 before 0.9.5
Timeline
- 2026-10-22: disclosed