CVE-2026-114110: uv vulnerable to arbitrary file deletion through RECORD entries
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.
Published Apr 10, 2026 · Updated Oct 23, 2026
Affected packages
uv
- Ecosystem
- PyPI
- Affected
- <= 0.11.5
- Fixed in
- 0.11.6
- Check
pip show uv
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 and newer of uv address the validation gap above, by removing invalid entries from RECORD files on wheel installation and ignoring RECORD paths that would escape the installation prefix on uninstall.
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.
Credited to konstin, zanieb, woodruffw, EliteTK, CodeByMoriarty.
References
- https://github.com/astral-sh/uv/security/advisories/GHSA-pjjw-68hj-v9mw
- https://github.com/astral-sh/uv/pull/18942
- https://github.com/astral-sh/uv/pull/18943
- https://github.com/astral-sh/uv/commit/7983c7a5bef236fd8a04580fcedae7bd5bde4cdb
- https://github.com/astral-sh/uv/commit/a0e461ac44851f9a0f6e8974733e77d46f7a9ea9
- https://github.com/astral-sh/uv/releases/tag/0.11.6
- https://nvd.nist.gov/vuln/detail/CVE-2026-114110
- https://www.vulncheck.com/advisories/astral-uv-before-0.11.6-arbitrary-file-deletion-via-wheel-record-entries
- https://github.com/advisories/GHSA-pjjw-68hj-v9mw
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesGHSA-hq85-5cpj-mr62
uv's bundled CA store trusts an emSign root whose intermediate CA keys are compromised
critical9.1Oct 20, 2026CVE-2026-104843
uv: Path traversal on Windows through wheel extraction
medium5.9Oct 5, 2026GHSA-4gg8-gxpx-9rph
uv is vulnerable to arbitrary file write through entry point names
mediumMay 29, 2026GHSA-pqhf-p39g-3x64
uv allows ZIP payload obfuscation through parsing differentials
medium6.8Oct 29, 2025GHSA-w476-p2h3-79g9
uv has differential in tar extraction with PAX headers
lowOct 21, 2025CVE-2025-54368
uv allows ZIP payload obfuscation through parsing differentials
medium6.8Aug 7, 2025
