<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-22T17:20:59.569221+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-115907</id>
    <title>CVE-2026-115907 — zip: legacy Shrink/Reduce/Implode decoder: denial of service from attacker-controlled ZIP64 uncompressed size</title>
    <updated>2026-11-22T17:20:59.570833+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> zip-rs zip2</p>
<p>zip is a zip library for Rust that supports reading and writing simple ZIP files. From 5.1.0 until 9.0.0, applications built with the legacy-zip feature can reserve output capacity from an attacker-controlled ZIP64 uncompressed size before validating the compressed stream. The ShrinkDecoder path in src/legacy/shrink.rs can panic with a capacity overflow during ZipArchive::extract, and the Reduce and Implode decoders contain the same unbounded preallocation pattern. An unhandled panic can terminate an archive-processing service. This issue is fixed in version 9.0.0.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-115907"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/rustsec-2026-0547</id>
    <title>RUSTSEC-2026-0547 — Legacy Shrink, Reduce and Implode decoders preallocate the declared uncompressed size</title>
    <updated>2026-11-22T17:20:59.570916+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: zip</p>
<p>With the `legacy-zip` feature, the decoders for the Shrink, Reduce and Implode compression methods reserved output capacity for the entry's declared uncompressed size before decoding anything. That size comes from the archive, and a ZIP64 entry can declare any 64-bit value, so reading or extracting a crafted entry of a few bytes panics with "capacity overflow" or fails a huge allocation.</p>
<p>An attacker who can supply an archive can stop a process that reads it, for example through `ZipArchive::extract`.</p>
<p>Only builds with the `legacy-zip` feature are affected; it is not enabled by default.</p>
<p>The fix caps the preallocation at 1 MiB, and such an entry now returns an error.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/rustsec-2026-0547"/>
  </entry>
</feed>
