Quick answers
- Is CVE-2026-119121 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119121 being exploited in the wild.
- How severe is CVE-2026-119121?
- Medium severity, with a CVSS score of 4.3, published 29 October 2026.
- Which products and versions are affected?
- Unclecode Crawl4AI 0.9.0 to 0.9.4.
- Is there a fix for CVE-2026-119121?
- Yes: fixed in 0.9.5. Until then: At your reverse proxy, reject crawler_config bodies where css_selector contains double quotes or where wait_for is not prefixed with css:. Additionally, issue API tokens only to trusted clients.</anigation> <parameter name="attack_vector">["network"] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119121 attacked?
- It is in a software library.
- Am I affected by CVE-2026-119121?
- 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
At your reverse proxy, reject crawler_config bodies where css_selector contains double quotes or where wait_for is not prefixed with css:. Additionally, issue API tokens only to trusted clients.</anigation> <parameter name="attack_vector">["network"]
Technical details
The vulnerability exists in AsyncPlaywrightCrawlerStrategy._crawl_web() and smart_wait() methods, which use unsafe string interpolation when processing css_selector and wait_for fields. An attacker can close the string literal in css_selector with a quote character to inject arbitrary JavaScript, or supply a js: prefixed condition in wait_for to execute JavaScript directly. Both fields are in the allowlist for untrusted requests and lack proper input validation on their content.
Affected products
- unclecode Crawl4AI 0.9.0 to 0.9.4
Timeline
- 2026-10-15: disclosed
- 2026-10-29: advisory