Security fix · CVE-2026-114110
uv vulnerable to arbitrary file deletion through RECORD entries
Published Apr 10, 2026 · catalog updated Oct 21, 2026 · uv vulnerable to arbitrary
Last checked Oct 28, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-114110. EPSS is 0.35%. Act only if a listed version of uv vulnerable to arbitrary is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (uv vulnerable to arbitrary).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High8.7
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.35%
- Remediation
- Advisory link
- Affected products
- PyPI uv
## Impact Wheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall. uv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbitrary files outside of the wheel’s installation prefix on uninstall. uv does not use the RECORD file to determine wheel file paths. Invalid RECORD entries cannot be used to create or modify files in arbitrary locations. Standards-compliant Python packaging tooling does not produce RECORD files that exhibit this behavior; an attacker must manually manipulate the RECORD. A user must install *and* uninstall the malformed wheel to be affected. An attack must guess the depth of the installation prefix path in order to target system files. Absolute paths in RECORD files are not allowed by the specification and, when present, uv always treats them as rooted in the wheel’s installation prefix. Absolute paths cannot be used to delete arbitrary files. Only files can be deleted, attempts to delete a directory via an invalid RECORD entry will fail. ## Patches Versions [0.11.6](https://github.com/astral-sh/uv/releases/tag/0.11.6) and newer of uv address the validation gap above, by [removing invalid entries from RECORD files on wheel installation](https://github.com/astral-sh/uv/pull/18943) and [ignoring RECORD paths that would escape the installation prefix on uninstall](https://github.com/astral-sh/uv/pull/18942). ## Workarounds Users are advised to upgrade to 0.11.6 or newer to address this advisory. Users should experience no breaking changes as a result of the patch above.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- PyPI uv0 → 0.11.6
How to fix CVE-2026-114110
Upgrade
CVE-2026-114110 lists a fix boundary at 0.11.6. Compare the installed build with that boundary before you change production.
Version check
Fixed in 0.11.6
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-114110. EPSS is 0.35%. Act only if a listed version of uv vulnerable to arbitrary is installed.
Which versions are affected?
Compare what you have installed with 0 → 0.11.6. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-22: Path Traversal; CWE-23. EPSS 0.35%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Apr 10, 2026 · GitHub Advisory Database
Detected
## Impact Wheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall. uv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbit
Oct 21, 2026 · GitHub Advisory Database
Fix available
uv fixed in 0.11.6
Oct 21, 2026 · GitHub Advisory Database
Fix available
uv fixed in 0.11.6
Oct 21, 2026 · GitHub Advisory Database
Updated
## Impact Wheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall. uv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbit
Oct 21, 2026 · NIST NVD
Updated
Astral uv before 0.11.6 contains a path traversal vulnerability that allows attackers to delete arbitrary files by supplying wheels with relative traversal paths in RECORD entries. Attackers can craft a malicious wheel whose RECORD references files outside the installation prefix, causing uv to delete those files when the user uninstalls the package.
Sources
- CVE.orgVulnerability recordCVE-2026-114110
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-114110
30-day exploitation probability 0.35%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-pjjw-68hj-v9mw
GitHub Advisory Database record mirrored by OSV.
github.com - NIST NVDVulnerability recordCVE-2026-114110
Astral uv before 0.11.6 contains a path traversal vulnerability that allows attackers to delete arbitrary files by supplying wheels with relative traversal paths in RECORD entries. Attackers can craft a malicious wheel whose RECORD references files outside the installation prefix
nvd.nist.gov - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-pjjw-68hj-v9mw
uv vulnerable to arbitrary file deletion through RECORD entries
osv.dev - PyPA Advisory DatabasePackage advisoryGHSA-pjjw-68hj-v9mw
uv vulnerable to arbitrary file deletion through RECORD entries
osv.dev
References
Freshness
Last verified in this catalog Oct 28, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 28, 2026
- CVE.orgOct 21, 2026
- PyPA Advisory DatabaseOct 21, 2026
- GitHub Advisory DatabaseOct 21, 2026
- OpenSSF OSV / OSV ScannerOct 21, 2026
- NIST NVDOct 21, 2026