GHSA-w476-p2h3-79g9
uv has differential in tar extraction with PAX headers
Impact
In versions 0.9.4 and earlier of uv, tar archives containing PAX headers with file size overrides were not handled properly. As a result, an attacker could contrive a source distribution (as a tar archive) that would extract differently when installed via uv versus other Python package installers.
The underlying parsing differential here originates with astral-tokio-tar, which disclosed this vulnerability as CVE-2025-62518.
In practice, the impact of this vulnerability is low: only source distributions can be formatted as tar archives, and source distributions execute arbitrary code at build/installation time by definition. Consequently, a parser differential in tar extraction is strictly less powerful than the capabilities already exposed to an attacker who has the ability to control source distributions.
However, this particular source of malleability in source distributions is unintentional and not operating by design, and therefore we consider it a vulnerability despite its overlap in capabilities with intended behavior.
Patches
Versions 0.9.5 and newer of uv address the vulnerability above. Users should upgrade to 0.9.5 or newer.
Workarounds
Users are advised to upgrade to version 0.9.5 or newer to address this advisory.
Users should experience no breaking changes as a result of the patch above.
References
- See CVE-2025-62518 for the corresponding advisory against astral-tokio-tar
What each source reports
GitHub AdvisoriesNo score
uv has differential in tar extraction with PAX headers
Impact
In versions 0.9.4 and earlier of uv, tar archives containing PAX headers with file size overrides were not handled properly. As a result, an attacker could contrive a source distribution (as a tar archive) that would extract differently when installed via uv versus other Python package installers.
The underlying parsing differential here originates with astral-tokio-tar, which disclosed this vulnerability as CVE-2025-62518.
In practice, the impact of this vulnerability is low: only source distributions can be formatted as tar archives, and source distributions execute arbitrary code at build/installation time by definition. Consequently, a parser differential in tar extraction is strictly less powerful than the capabilities already exposed to an attacker who has the ability to control source distributions.
However, this particular source of malleability in source distributions is unintentional and not operating by design, and therefore we consider it a vulnerability despite its overlap in capabilities with intended behavior.
Patches
Versions 0.9.5 and newer of uv address the vulnerability above. Users should upgrade to 0.9.5 or newer.
Workarounds
Users are advised to upgrade to version 0.9.5 or newer to address this advisory.
Users should experience no breaking changes as a result of the patch above.
References
- See CVE-2025-62518 for the corresponding advisory against astral-tokio-tar
- Record
GHSA-w476-p2h3-79g9- Weakness
- CWE-843
- Updated
- 2026-11-02
OSVNo score
uv has differential in tar extraction with PAX headers
Impact
In versions 0.9.4 and earlier of uv, tar archives containing PAX headers with file size overrides were not handled properly. As a result, an attacker could contrive a source distribution (as a tar archive) that would extract differently when installed via uv versus other Python package installers.
The underlying parsing differential here originates with astral-tokio-tar, which disclosed this vulnerability as CVE-2025-62518.
In practice, the impact of this vulnerability is low: only source distributions can be formatted as tar archives, and source distributions execute arbitrary code at build/installation time by definition. Consequently, a parser differential in tar extraction is strictly less powerful than the capabilities already exposed to an attacker who has the ability to control source distributions.
However, this particular source of malleability in source distributions is unintentional and not operating by design, and therefore we consider it a vulnerability despite its overlap in capabilities with intended behavior.
Patches
Versions 0.9.5 and newer of uv address the vulnerability above. Users should upgrade to 0.9.5 or newer.
Workarounds
Users are advised to upgrade to version 0.9.5 or newer to address this advisory.
Users should experience no breaking changes as a result of the patch above.
References
- See CVE-2025-62518 for the corresponding advisory against astral-tokio-tar
- Record
GHSA-w476-p2h3-79g9- Weakness
- CWE-843
- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
uvPyPI | through 0.9.4 | 0.9.5 |
uvPyPI | before 0.9.5, plus listed versions 0.0.50.1.00.1.10.1.100.1.11 Show 45 moreShow less0.1.120.1.130.1.140.1.150.1.160.1.170.1.180.1.190.1.20.1.200.1.210.1.220.1.230.1.240.1.250.1.260.1.270.1.280.1.290.1.30.1.300.1.310.1.320.1.330.1.340.1.350.1.360.1.370.1.380.1.390.1.40.1.400.1.410.1.420.1.430.1.440.1.450.1.50.1.60.1.70.1.80.1.90.2.00.2.10.2.10 | 0.9.5 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-w476-p2h3-79g9 is a vulnerability with no CVSS score yet in uv, published October 21, 2025. No source lists public exploit code. Fixed in uv 0.9.5.
References
github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9
Left out here: 175 versions. The JSON record has them.