Live › vulnerability › CVE-2025-13327
uv, the Python package manager, can be fooled by specially crafted ZIP archives that parse differently in different tools, so a malicious package hides code from inspection. An attacker gets code execution on the machine when a user installs or resolves that package.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 00:35 UTC, 0h before NVD. All times on this page are UTC.
Teams and developers who run uv to install or resolve Python packages, including in CI and build pipelines. Systems that never run uv, or only install from a trusted, pinned set of packages, are much less exposed. The sources do not describe further configuration conditions.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| uv | cargo | < 0.9.6 | 0.9.6 |
| astral uv | vendor | < 0.9.6 | 0.9.6 |
uv --version and compare against the fixed version below.uv runs that install packages from unfamiliar or untrusted indexes.uv upgrade to 0.9.6 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw was found in uv. This vulnerability allows an attacker to execute malicious code during package resolution or installation via specially crafted ZIP (Zipped Information Package) archives that exploit parsing differentials, requiring user interaction to install an attacker-controlled package.
This page as .md · .json · in your agent: get_signal("CVE-2025-13327")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.