# CVE-2026-119118: Crawl4AI before 0.9.5 Improper Certificate Validation via Hard-coded Chromium Flags


- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/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-495r-f2mc-w3jj, GHSA-j2qh-f73r-mg3q

## What is CVE-2026-119118?

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

### Official description

Crawl4AI before 0.9.5 contains an improper certificate validation vulnerability that allows network attackers to intercept crawls because Chromium always launches with --ignore-certificate-errors. Man-in-the-middle or DNS-controlling attackers can serve forged content to the crawler and read cookies and headers sent, while hard-coded --no-sandbox also overrides CRAWL4AI_CHROMIUM_SANDBOX.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2026-119118 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119118 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119118 is a high-severity vulnerability in unclecode crawl4ai, published on 29 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119118 exists.

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-119118/ (Markdown: https://insights.sbomify.com/CVE-2026-119118/index.md)
```

## Sources

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

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