Advisory

GHSA-4gg8-gxpx-9rph

Also known as: CVE-2026-114109

Summary

uv is vulnerable to arbitrary file write through entry point names

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-05-29 19:26 UTC
Modified
2026-10-21 10:57 UTC

Affected packages and fixes

uv

PyPI · All systems

Affected

  • introduced 0, fixed 0.11.15 (ecosystem)

Fixed versions

0.11.15

Fix

  • Fixed version 0.11.15
    pip install --upgrade uv==0.11.15

uv

crates.io · All systems

Affected

  • introduced 0, fixed 0.11.15 (semver)

Fixed versions

0.11.15

Fix

  • Fixed version 0.11.15
    cargo update -p uv --precise 0.11.15

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences