GHSA-pjjw-68hj-v9mw: Uv Uv Vulnerable To Arbitrary File Vulnerability

LOW
Share
CWE-22
Published
Advisory Summary

GHSA-pjjw-68hj-v9mw is a LOW uv vulnerable to arbitrary file vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Uv libraries in the PyPI ecosystem. The issue involves uv vulnerable to arbitrary file deletion through record entries. Remediation is available by upgrading affected packages to version 0.11.6.

GHSA-pjjw-68hj-v9mw at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-pjjw-68hj-v9mw
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Uv
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-pjjw-68hj-v9mw

To remediate this vulnerability, upgrade all affected Uv dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

uv fixed: 0.11.6 
pip install uv>=0.11.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show uv

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-pjjw-68hj-v9mw, inspect your installed packages using pip:

pip show uv

Analyze the terminal output to locate any version of Uv in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.11.6), your application is affected.

Note: The pip show uv command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Uv, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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.

GHSA-pjjw-68hj-v9mw Affected Uv Versions

1 component(s)
Fixed Versions:
0.11.6
Product / Package Ecosystem Affected Versions Fixed Version
uv
pypi/uv
PyPI
< 0.11.6
0.11.6

References

GitHub Advisory / Wiki ADVISORY
https://github.com/astral-sh/uv/security/advisories/GHSA-pjjw-68hj-v9mw
Uv Source Repository REPOSITORY
https://github.com/astral-sh/uv/pull/18942
Uv Source Repository REPOSITORY
https://github.com/astral-sh/uv/pull/18943
Security Fix Commit FIX COMMIT
https://github.com/astral-sh/uv/commit/7983c7a5bef236fd8a04580fcedae7bd5bde4cdb
Security Fix Commit FIX COMMIT
https://github.com/astral-sh/uv/commit/a0e461ac44851f9a0f6e8974733e77d46f7a9ea9
Uv Source Repository REPOSITORY
https://github.com/astral-sh/uv
Uv Release RELEASE
https://github.com/astral-sh/uv/releases/tag/0.11.6

Frequently Asked Questions

What is GHSA-pjjw-68hj-v9mw?
GHSA-pjjw-68hj-v9mw is a security vulnerability in Uv involving uv vulnerable to arbitrary file deletion through RECORD entries under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Uv versions are affected?
Affected versions include releases prior to 0.11.6 across affected packages: uv.
What version fixes GHSA-pjjw-68hj-v9mw?
Upgrading to 0.11.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is uv affected?
Yes, uv is affected in releases prior to 0.11.6. Upgrade your dependency to 0.11.6 or later.
What CWE is associated with GHSA-pjjw-68hj-v9mw?
GHSA-pjjw-68hj-v9mw is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check PyPI dependencies for GHSA-pjjw-68hj-v9mw?
Run the dependency tree command: 'pip show uv'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pjjw-68hj-v9mw",
  "modified" : "2026-04-10T19:39:15Z",
  "published" : "2026-04-10T19:39:15Z",
  "aliases" : [ ],
  "summary" : "uv vulnerable to arbitrary file deletion through RECORD entries",
  "details" : "## Impact\n\nWheel 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.\n\nuv 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.\n\nuv 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.\n\nStandards-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.\n\nAbsolute 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.\n\nOnly files can be deleted, attempts to delete a directory via an invalid RECORD entry will fail.\n\n## Patches\n\nVersions [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).\n\n## Workarounds\n\nUsers are advised to upgrade to 0.11.6 or newer to address this advisory.\n\nUsers should experience no breaking changes as a result of the patch above.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "uv"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.11.6"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.11.5"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/uv/security/advisories/GHSA-pjjw-68hj-v9mw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/uv/pull/18942"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/uv/pull/18943"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/uv/commit/7983c7a5bef236fd8a04580fcedae7bd5bde4cdb"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/uv/commit/a0e461ac44851f9a0f6e8974733e77d46f7a9ea9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/astral-sh/uv"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/uv/releases/tag/0.11.6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-10T19:39:15Z",
    "nvd_published_at" : null
  }
}