Skip to main content

Astral uv EUVDEUVD-2025-211142

| CVE-2025-71437 HIGH
Path Traversal (CWE-22)
2026-10-21 VulnCheck GHSA-5gxr-jwgw-qf6w
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Publish malicious sdist to index
  2. Delivery
    Victim installs package with uv
  3. Exploit
    Symlink chain redirects tar extraction
  4. Execution
    Arbitrary file write outside prefix
  5. Impact
    Code execution via planted file

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the victim to install a specially crafted source distribution (sdist) using a vulnerable uv version (before 0.8.22) where the install path goes through uv's sdist tar-extraction code; the malicious archive must contain a crafted symlink sequence that resolves outside the intended extraction prefix. Limiting factors: the attacker does not run code on the target directly - a user must actively choose to install the attacker-controlled package (so curated, pinned, or hash-verified dependency sources materially reduce exposure), and only uv (not other installers) is affected. Installing only trusted/first-party packages, or upgrading to uv 0.8.22+, removes the condition.

Impact

This is a supply-chain path-traversal flaw (CWE-22) in Astral uv's sdist tar extraction, scored CVSS 4.0 8.7 (High) by the reporter. The provided vector (AV:N/AC:L/PR:N/UI:N/VC:H/VI:N/VA:N) conflicts with the description: the described impact is writing arbitrary files OUTSIDE the extraction prefix, which is an INTEGRITY impact, yet the vector records confidentiality-high (VC:H) and integrity-none (VI:N) - these appear transposed and should be treated with caution. The vector also lists UI:N, but exploitation realistically requires a victim to install the attacker's malicious sdist, i.e. user action is needed - so the 'unauthenticated, no-interaction' reading overstates ease. No EPSS score, no CISA KEV listing, and no public POC are present in the input, so there is no evidence of active exploitation; exploitation status is 'no public exploit identified at time of analysis.' Net: this is a genuine, high-impact issue (arbitrary file write via a crafted package can lead to code execution), but it is a social/supply-chain vector requiring the victim to install a malicious package rather than a directly remote-triggerable server bug - real priority for anyone installing untrusted sdists, lower urgency where package sources are curated/pinned.

Exploit ScenarioDerived

An attacker publishes a malicious Python source distribution (sdist) to a package index (or supplies it via a dependency) containing a crafted sequence of symlinks in its tar archive. When a victim installs the package with a vulnerable uv (before 0.8.22), the symlink chain redirects extraction writes outside the intended install prefix, dropping attacker-controlled files into arbitrary filesystem locations (e.g. shell profiles or startup scripts), which can lead to code execution. No public exploit code is identified in the provided data; disclosure is via a VulnCheck advisory and a GitHub Security Advisory (GHSA-7j9j-68r2-f35q).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Installing a malicious source distribution with Astral uv versions before 0.8.22 can let a crafted chain of symlinks redirect file writes outside the intended extraction prefix, producing arbitrary file writes on the installer’s filesystem with high integrity impact but no confidentiality or availability impact. The reporter scored this CVSS 4.0 8.7 High, while independent analysis assesses CVSS 3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N and stresses that a user must actively install the attacker-controlled package; no public exploit was identified at time of analysis. Upgrading to uv 0.8.22 or later removes the vulnerable extraction behavior.

RemediationAI

Vendor-released patch: upgrade Astral uv to 0.8.22 or later; this is the primary fix and removes the vulnerable sdist tar-extraction behavior. See the GHSA advisory at https://github.com/astral-sh/uv/security/advisories/GHSA-7j9j-68r2-f35q and the VulnCheck advisory at https://www.vulncheck.com/advisories/astral-uv-through-0.8.21-path-traversal-via-symlinks-in-sdist-tar-extraction. If immediate upgrade is not possible, restrict uv installs to curated, first-party packages and enforce pinned, hash-verified lockfiles, which materially reduces exposure by preventing installation of attacker-controlled sdists but does not fix the underlying extraction path and may block legitimate third-party sdists; do not install untrusted source distributions with a vulnerable uv version.

Affected VersionsENISA

uv 0 ≤0.8.21

Affected Packages

euvd uv no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Astral uv is a Python package installer and resolver that downloads and extracts source distributions (sdists), which are tar archives, before building or installing them. The flaw is a CWE-22 path traversal in uv’s sdist tar extraction: insufficient containment of symlink targets lets a crafted sequence of symlinks cause later file writes to resolve outside the destination prefix. CPE data maps the affected product to cpe:2.3:a:astral-sh:uv:*:*:*:*:*:*:*:*; the GHSA advisory and VulnCheck reference identify the fixed release as 0.8.22. The independent assessment rates it network-reachable, low-complexity, no privileges required, user interaction required, scope changed, with high integrity impact only (C:N/I:H/A:N).

Know when Uv gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 7.4 HIGH

Victim must install the malicious sdist (UI:R); arbitrary file write outside the prefix affects the host beyond uv (S:C) and is an integrity impact (I:H), not confidentiality.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
Red Hat 5.5 MEDIUM

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Astral uv before 0.8.22 contains a path traversal vulnerability in source distribution (sdist) tar extraction that allows a specially crafted sequence of symlinks to redirect file writes outside the intended extraction prefix. Attackers can publish a malicious sdist that, when installed by a victim, writes arbitrary files to filesystem locations outside the installation prefix.

Technical POC Analysis

Evidence base: GHSA-7j9j-68r2-f35q only.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

Astral uv versions before 0.8.22 contain a high-severity flaw that lets a malicious source distribution write files outside the intended extraction directory, threatening the integrity of developer workstations and CI/CD build environments. Leadership should care because this is a supply-chain risk that can silently alter code or configuration on systems where developers install third-party Python packages; however, exploitation requires a user to install the attacker-controlled package, and no public exploit identified at time of analysis.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 80% exploitable
Prevalence
High
fast-growing Python package manager, widely used across dev and CI pipelines
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Related Vulnerabilities in Astral uv Path Traversal in Package Extraction

View all 3

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy