<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T21:07:11.658573+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2025-54368</id>
    <title>CVE-2025-54368 — uv is vulnerable to ZIP payload obfuscation through parsing differentials</title>
    <updated>2026-10-02T21:07:11.808463+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> astral-sh uv</p>
<p>uv is a Python package and project manager written in Rust. In versions 0.8.5 and earlier, remote ZIP archives were handled in a streamwise fashion, and file entries were not reconciled against the archive's central directory. An attacker could contrive a ZIP archive that would extract with legitimate contents on some package installers, and malicious contents on others due to multiple local file entries. An attacker could  also contrive a "stacked" ZIP input with multiple internal ZIPs, which would be handled differently by different package installers. The attacker could choose which installer to target in both scenarios. This issue is fixed in version 0.8.6. To work around this issue, users may choose to set UV_INSECURE_NO_ZIP_VALIDATION=1 to revert to the previous behavior.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-54368"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-8qf3-x8v5-2pj8</id>
    <title>GHSA-8qf3-x8v5-2pj8 — uv allows ZIP payload obfuscation through parsing differentials</title>
    <updated>2026-10-02T21:07:11.808579+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: uv</p>
<p>## Impact</p>
<p>In versions 0.8.5 and earlier of uv, remote ZIP archives were handled in a streamwise fashion, and file entries were not reconciled against the archive's central directory. This enabled two parser differentials against other Python package installers:</p>
<p>1. An attacker could contrive a ZIP archive that would extract with legitimate contents on some package installers, and malicious contents on others due to multiple local file entries. The attacker could choose which installer to target.
2. An attacker could contrive a "stacked" ZIP input with multiple internal ZIPs, which would be handled differently by different package installers. The attacker could choose which installer to target.</p>
<p>In both cases, the outcome is that an attacker can produce a ZIP with a consistent digest that expands differently with different installers.</p>
<p>The [ZIP standard](https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT) is ambiguous with respect to these behavior differentials. Consequently, these same differentials may be accepted ZIP parsers other than those used in uv. This advisory is for uv in particular, but all consumers of ZIP-based Python package distributions, e.g., pip, are potentially susceptible to similar parser differentials in other ZIP parsers.</p>
<p>The practical impact of these differentials is limited by a number of factors:</p>
<p>- To be compromised via this vulnerability, user interaction of some sort is required. In particular, the user must run `uv install $package`…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-8qf3-x8v5-2pj8"/>
  </entry>
</feed>
