GHSA-4gg8-gxpx-9rph: Uv Uv Is Vulnerable To Arbitrary Vulnerability

MODERATE
CWE-22
Published
Advisory Summary

GHSA-4gg8-gxpx-9rph is a MODERATE uv is vulnerable to arbitrary 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 is vulnerable to arbitrary file write through entry point names. Remediation is available by upgrading affected packages to version 0.11.15.

GHSA-4gg8-gxpx-9rph at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-4gg8-gxpx-9rph
Severity MODERATE
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-4gg8-gxpx-9rph

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.15
pip install uv>=0.11.15
uv fixed: 0.11.15
Upgrade uv to 0.11.15
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-4gg8-gxpx-9rph, 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.15), 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 In versions of uv prior to 0.11.15, when installing a distribution containing an entry point specification (under `console_scripts` or `gui_scripts`), uv would place the generated entry point according to the given name even if doing so resulted in a path outside of the environment's scripts directory. A malicious wheel could use this to place an executable outside of the intended environment, including in a directory already present on the user's `PATH`. This could shadow or overwrite an existing executable and potentially result in unexpected code execution under the wheel's control, even if the wheel's installation environment was not explicitly added to `PATH` by the user. In order to exploit this vulnerability, the attacker must induce their target into installing a malicious wheel. ### Patches uv 0.11.15 and newer address this vulnerability. Users are encouraged to upgrade to 0.11.15. ### Workarounds There is no workaround other than upgrading to uv 0.11.15.

GHSA-4gg8-gxpx-9rph Affected Uv Versions

2 component(s)
Fixed Versions:
0.11.15
Product / Package Ecosystem Affected Versions Fixed Version
uv
PyPI
< 0.11.15
0.11.15
uv
crates.io
< 0.11.15
0.11.15

References

Frequently Asked Questions

What is GHSA-4gg8-gxpx-9rph?
GHSA-4gg8-gxpx-9rph is a security vulnerability in Uv involving uv is vulnerable to arbitrary file write through entry point names 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.15 across affected packages: uv.
What version fixes GHSA-4gg8-gxpx-9rph?
Upgrading to 0.11.15 (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.15. Upgrade your dependency to 0.11.15 or later.
What CWE is associated with GHSA-4gg8-gxpx-9rph?
GHSA-4gg8-gxpx-9rph 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-4gg8-gxpx-9rph?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4gg8-gxpx-9rph",
  "modified" : "2026-05-29T19:26:33Z",
  "published" : "2026-05-29T19:26:33Z",
  "aliases" : [ ],
  "summary" : "uv is vulnerable to arbitrary file write through entry point names",
  "details" : "### Impact\n\nIn versions of uv prior to 0.11.15, when installing a distribution containing an entry point specification (under `console_scripts` or `gui_scripts`), uv would place the generated entry point according to the given name even if doing so resulted in a path outside of the environment's scripts directory.\n\nA malicious wheel could use this to place an executable outside of the intended environment, including in a directory already present on the user's `PATH`. This could shadow or overwrite an existing executable and potentially result in unexpected code execution under the wheel's control, even if the wheel's installation environment was not explicitly added to `PATH` by the user.\n\nIn order to exploit this vulnerability, the attacker must induce their target into installing a malicious wheel.\n\n### Patches\n\nuv 0.11.15 and newer address this vulnerability. Users are encouraged to upgrade to 0.11.15.\n\n### Workarounds\n\nThere is no workaround other than upgrading to uv 0.11.15.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "uv"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.11.15"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "uv"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.11.15"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/astral-sh/uv/security/advisories/GHSA-4gg8-gxpx-9rph"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/astral-sh/uv"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-29T19:26:33Z",
    "nvd_published_at" : null
  }
}