ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-114109

uv is vulnerable to arbitrary file write through entry point names

Published May 29, 2026 · catalog updated Oct 21, 2026 · uv is vulnerable to

Check if you run it

No confirmed exploitation is on record for CVE-2026-114109. EPSS is 0.38%. Act only if a listed version of uv is vulnerable to is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (uv is vulnerable to).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.38%
Remediation
Advisory link
Affected products
PyPI uv · crates.io uv

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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • PyPI uv0 → 0.11.15
  • crates.io uv0 → 0.11.15

How to fix CVE-2026-114109

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-114109. EPSS is 0.38%. Act only if a listed version of uv is vulnerable to is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.11.15. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-22: Path Traversal. EPSS 0.38%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 29, 2026 · GitHub Advisory Database

    Detected

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

  2. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    uv fixed in 0.11.15; uv fixed in 0.11.15

  3. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    uv fixed in 0.11.15

  4. Oct 21, 2026 · GitHub Advisory Database

    Updated

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

Sources

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.