uv before 0.11.15 contains a path traversal vulnerability that allows malicious wheels to write files outside the scripts directory via crafted console_scripts or gui_scripts entry point names. Attackers who induce users to install a malicious wheel can place executables in PATH directories, shadowing or overwriting existing binaries for code execution.
CVE-2026-114109
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-21. A secondary CVSS source baseline 8.8; sources differ by 0.0.
Also known asEUVD-2026-106912 (ENISA EUVD) · GHSA-m8vc-5xpp-qpqf (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHhigh confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 32nd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 21, 2026
Last Modified
October 28, 2026
Advisory Details (2)
Auto-updated Oct 21, 2026uv before 0.11.15 Arbitrary File Write via Entry Point Names | Advisories | VulnCheck
https://www.vulncheck.com/advisories/uv-before-0.11.15-arbitrary-file-write-via-entry-point-namesArbitrary file write through entry point names · Advisory · astral-sh/uv · GitHub
https://github.com/astral-sh/uv/security/advisories/GHSA-4gg8-gxpx-9rphVendor Advisories for CVE-2026-114109(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:91236Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat AI Base Images 3.0.7 (CUDA)
- RHSA-2026:91219Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat AI Base Images 3.0.7 (ROCm)
- GHSA-m8vc-5xpp-qpqfGitHub Security AdvisoriesHigh
uv before 0.11.15 contains a path traversal vulnerability that allows malicious wheels to write...
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 24× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-28 17:26 UTCEG score recompute
- 2026-10-28 17:26 UTCGHSA enrichmentGHSA-m8vc-5xpp-qpqf · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-28 16:25 UTCEG score recompute
- 2026-10-28 16:25 UTCGHSA enrichmentGHSA-m8vc-5xpp-qpqf · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-27 20:43 UTCEG score recompute
- 2026-10-27 20:43 UTCGHSA enrichmentGHSA-m8vc-5xpp-qpqf · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-25 14:50 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-22 17:47 UTCEG score recompute
- 2026-10-22 17:47 UTCGHSA enrichmentGHSA-m8vc-5xpp-qpqf · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-21 01:26 UTCEG score recompute
- 2026-10-21 00:47 UTCEG score recomputeFirst assessed: 8.8 HIGH
- 2026-10-21 00:47 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
4 showncrates.io:uv · PyPI:uv
Frequently asked(5)
What is CVE-2026-114109?
When was CVE-2026-114109 made public?
Is CVE-2026-114109 actively exploited?
What is the CVSS score of CVE-2026-114109?
How do I remediate CVE-2026-114109?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-114109
Is Your Infrastructure Affected by CVE-2026-114109?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.