# CVE-2026-111449: Race condition in Wheels

> An attacker can exploit a race condition to view sensitive exception details if debug access is enabled, requiring an upgrade to fix.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-8r22-vwcc-v55m, GHSA-rh8q-647v-56rc

## What is CVE-2026-111449?

CVE-2026-111449 is a medium-severity vulnerability in Wheels, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wheels 3.0.0 through 4.1.1 can disclose detailed exceptions when allowIPBasedDebugAccess=true (disabled by default). An allowed administrator request changes error/debug-display settings in shared application scope. If it overlaps with an unauthorized client's request that raises an error, that client can receive full exception details, including tag context or a serialized exception, and any sensitive data they contain. This race does not bypass the production gate protecting developer tools. This is fixed in 4.1.2.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

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

## Is CVE-2026-111449 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111449 is a medium-severity vulnerability in Wheels, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111449 in the wild and no public exploit code.

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

## Sources

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

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