GHSA-4GG8-GXPX-9RPH
Vulnerability from github – Published: 2026-05-29 19:26 – Updated: 2026-05-29 19:26Impact
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.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "uv"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.11.15"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "crates.io",
"name": "uv"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.11.15"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-29T19:26:33Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"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\u0027s 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\u0027s `PATH`. This could shadow or overwrite an existing executable and potentially result in unexpected code execution under the wheel\u0027s control, even if the wheel\u0027s 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.",
"id": "GHSA-4gg8-gxpx-9rph",
"modified": "2026-05-29T19:26:33Z",
"published": "2026-05-29T19:26:33Z",
"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"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "uv is vulnerable to arbitrary file write through entry point names"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.