# CVE-2026-119121: Crawl4AI 0.9.0 before 0.9.5 JavaScript Injection via css_selector and wait_for


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-6fxw-998x-jq4q, GHSA-qj46-wp7m-rgj8

## What is CVE-2026-119121?

CVE-2026-119121 is a medium-severity vulnerability in unclecode crawl4ai, published on 29 Oct 2026. 

### Official description

Crawl4AI from 0.9.0 before 0.9.5 contains a JavaScript injection vulnerability in the Docker API server that allows authenticated API clients to run arbitrary JavaScript in the crawl page via allowlisted css_selector and wait_for fields. Attackers can inject quotes into css_selector or supply js: conditions in wait_for, bypassing the js_code block to alter page state and returned crawl content.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2026-119121?


## How do I fix CVE-2026-119121?

No fix has been published for CVE-2026-119121 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119121 being exploited?

There is no known exploitation of CVE-2026-119121 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119121 and fix it if it is affected.

What it is: CVE-2026-119121 is a medium-severity vulnerability in unclecode crawl4ai, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119121 in the wild and no public exploit code.

Affected product: unclecode crawl4ai. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119121/ (Markdown: https://insights.sbomify.com/CVE-2026-119121/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119121
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119121
- OSV: https://osv.dev/vulnerability/CVE-2026-119121

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119121/
Summaries are generated and may contain mistakes; the official description above is the record.