# CVE-2026-111448: Path traversal in Wheels

> Attackers can bypass path containment checks via case-insensitive comparisons to access files outside the intended root or write to sibling directories.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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-55rj-mxqv-p89q, GHSA-m63x-8m98-225v

## What is CVE-2026-111448?

CVE-2026-111448 is a low-severity path traversal 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 4.0.0 through 4.1.2 uses case-insensitive comparisons in path-containment checks on case-sensitive filesystems. Canonical-path checks for zip entries, package mappings, development assets/docs, guide images and image tags can accept paths through an existing symlink to a case-distinct sibling directory, allowing access outside the intended root, including limited file disclosure. Separately, the CLI database-dump output check can write outside the application root to an existing writable case-distinct sibling directory; that action requires the CLI POST, loopback and password gate. This is fixed in 4.2.0.

Weakness: CWE-178 (Improper Handling of Case Sensitivity)

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


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

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

## Is CVE-2026-111448 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111448 is a low-severity path traversal 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-111448 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-111448/ (Markdown: https://insights.sbomify.com/CVE-2026-111448/index.md)
```

## Sources

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

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