Quick answers
- Is CVE-2026-119118 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119118 being exploited in the wild.
- How severe is CVE-2026-119118?
- Medium severity, with a CVSS score of 6.5, published 29 October 2026.
- Which products and versions are affected?
- Unclecode Crawl4AI before 0.9.5.
- Is there a fix for CVE-2026-119118?
- Yes: fixed in 0.9.5. Until then: Keep the crawler on a trusted network path with a trusted DNS resolver to reduce exposure to man-in-the-middle attacks until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119118 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119118?
- 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
Keep the crawler on a trusted network path with a trusted DNS resolver to reduce exposure to man-in-the-middle attacks until upgrading.
Technical details
The vulnerability stems from hard-coded --ignore-certificate-errors and --ignore-certificate-errors-spki-list flags passed to Chromium at launch, which cannot be overridden by configuration options. Network-based or DNS-controlling attackers can perform man-in-the-middle attacks to serve forged content and exfiltrate request data. Additionally, hard-coded --no-sandbox bypasses the intended Chromium renderer sandbox when CRAWL4AI_CHROMIUM_SANDBOX is enabled.
Affected products
- unclecode Crawl4AI before 0.9.5
Timeline
- 2026-10-15: disclosed
- 2026-10-29: advisory