NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

GHSA-4gg8-gxpx-9rph: uv is vulnerable to arbitrary file write through entry point names

medium

Impact In versions of uv prior to 0.11.15, when installing a distribution containing an entry point specification (under consolescripts or guiscripts), 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.

Published May 29, 2026

Affected packages

uv

Ecosystem
PyPI
Affected
< 0.11.15
Fixed in
0.11.15
Check
pip show uv

uv

Ecosystem
Rust (crates.io)
Affected
< 0.11.15
Fixed in
0.11.15
Check
cargo tree -i uv

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to zsol, zanieb.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More PyPI vulnerabilities

All PyPI entries