uv is vulnerable to arbitrary file write through entry point names
Exact source revision recorded 24 Oct 2026 13:19:54 UTC. It does not establish the source's current position. Latest evidence.
osv · GHSA-4gg8-gxpx-9rph
Published### 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.
- Source published
- 29 May 2026 19:26:33 UTC
- Source modified
- 21 Oct 2026 10:57:22 UTC
- Observed here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
Publisher rating · MODERATE