Live › vulnerability › CVE-2026-114110
Go to dashboarduv 0.11.5 and earlier trusts relative paths in a wheel's RECORD file when uninstalling, so a crafted wheel can make uv delete arbitrary files outside its installation prefix. Only files can be removed, and the attacker must guess the path depth to hit system files.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 20:59 UTC, 1h before NVD. All times on this page are UTC.
Teams running uv or earlier that install a wheel from an untrusted or malicious source and later uninstall it. Standard packaging tools do not produce these RECORD entries, so routine installs from PyPI are unlikely to be the vector. Teams that only use current uv or only install trusted packages can skip it.
0.11.5| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| uv | pypi | <= 0.11.5 | 0.11.6 |
uv --version and see whether it reports 0.11.5 or older.0.11.6 or newer.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
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.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-114110")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.