# CVE-2026-109237: Crawl4AI 0.9.0 before 0.9.4 Untrusted Config Gate Bypass Leaks Environment Variables

> Attackers can bypass config restrictions to leak environment variables and forge admin JWTs, compromising the Crawl4AI web crawler library.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-5w5p-vcv6-mm3f, GHSA-r6v9-2q53-jfjp

## What is CVE-2026-109237?

CVE-2026-109237 is a high-severity unsafe deserialization vulnerability in unclecode crawl4ai, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Crawl4AI from 0.9.0 before 0.9.4 contains an untrusted-config gate bypass that allows non-admin API clients to construct forbidden config objects by wrapping them in dict-type wrappers. Attackers can send a laundered LLMConfig with api_token set to an env reference via /config/dump to read SECRET_KEY and provider keys, enabling admin JWT forgery.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-109237 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109237 is a high-severity unsafe deserialization vulnerability in unclecode crawl4ai, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109237 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-109237/ (Markdown: https://insights.sbomify.com/CVE-2026-109237/index.md)
```

## Sources

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

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