Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 5.3, published 21 October 2026.
- Which products and versions are affected?
- Astral Uv before 0.11.6; uv (PyPI) < 0.11.6, ECOSYSTEM:introduced=0.
- Is there a fix for This vulnerability?
- Yes: fixed in 0.11.6. Until then: Upgrade to uv 0.11.6 or newer. Users should avoid installing wheels from untrusted sources. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run Astral Uv or uv (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.11.6
Upgrade to uv 0.11.6 or newer. Users should avoid installing wheels from untrusted sources.
Technical details
A path traversal vulnerability in uv before 0.11.6 allows RECORD entries in wheel packages to reference files outside the installation prefix using relative paths. During uninstall, uv does not validate RECORD entries, respecting them to determine which files to remove. An attacker can craft a wheel with relative path traversal sequences (e.g., `../../../etc/passwd`) in the RECORD; uninstallation of such a wheel would delete those files if the attacker correctly guesses the installation prefix depth. The attack requires user interaction (install and uninstall of a malicious wheel) and does not permit arbitrary file creation or modification.
Affected products
- Astral uv before 0.11.6
Timeline
- 2026-04-09: disclosed
- 2026-04-09: patched: Version 0.11.6 released with validation of RECORD entries