Quick answers
- Is CVE-2026-119119 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119119 being exploited in the wild.
- How severe is CVE-2026-119119?
- High severity, with a CVSS score of 7.5, published 29 October 2026.
- Which products and versions are affected?
- Unclecode Crawl4AI before 0.9.5.
- Is there a fix for CVE-2026-119119?
- Yes: fixed in 0.9.5. Until then: Enable JWT authentication by setting security.jwt_enabled and restrict API access to trusted networks only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119119 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119119?
- 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
Enable JWT authentication by setting security.jwt_enabled and restrict API access to trusted networks only.
Technical details
The vulnerability exists in the _clamp_untrusted() function in crawl4ai/async_configs.py, which fails to cap three fields (delay_before_return_html, mean_delay, and max_range) in untrusted CrawlerRunConfig bodies, even though similar time-related fields like page_timeout are properly clamped. An attacker can send huge values to /crawl or /crawl/stream endpoints over the network without authentication to hold browser pages indefinitely or stall the rate limiter, exhausting the page pool and blocking other concurrent crawls.
Affected products
- unclecode Crawl4AI before 0.9.5
Timeline
- 2026-10-15: disclosed
- 2026-10-29: advisory