<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 09 Nov 2026 11:06:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-115909 — zip: Unbounded Symlink-Target Handling Can Abort Or Exhaust Memory During Extraction</title>
      <link>https://db.gcve.eu/vuln/cve-2026-115909</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; zip-rs zip2&lt;/p&gt;
&lt;p&gt;zip is a zip library for Rust that supports reading and writing simple ZIP files. From 1.3.0 until 9.0.0, ZipArchive::extract in src/read/mod.rs calls Vec::with_capacity for a symbolic link target using the attacker-controlled ZIP64 uncompressed_size before reading entry data. A small archive can request an impossible capacity, causing the infallible allocation path to abort the process before the entry is validated. The failure cannot be contained with catch_unwind or a worker thread, allowing repeated denial of service in archive-processing applications. This issue is fixed in version 9.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; zip-rs zip2&lt;/p&gt;
&lt;p&gt;zip is a zip library for Rust that supports reading and writing simple ZIP files. From 1.3.0 until 9.0.0, ZipArchive::extract in src/read/mod.rs calls Vec::with_capacity for a symbolic link target using the attacker-controlled ZIP64 uncompressed_size before reading entry data. A small archive can request an impossible capacity, causing the infallible allocation path to abort the process before the entry is validated. The failure cannot be contained with catch_unwind or a worker thread, allowing repeated denial of service in archive-processing applications. This issue is fixed in version 9.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-115909</guid>
    </item>
    <item>
      <title>RUSTSEC-2026-0429 — zip: `ZipArchive::extract` aborts the process on a symlink entry with a large declared size</title>
      <link>https://db.gcve.eu/vuln/rustsec-2026-0429</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: zip&lt;/p&gt;
&lt;p&gt;`ZipArchive::extract()` sizes the symlink-target buffer from the uncompressed
size declared in the central directory record, before reading a single byte of
entry data:&lt;/p&gt;
&lt;p&gt;```rust
let mut target = Vec::with_capacity(file.size() as usize);
```&lt;/p&gt;
&lt;p&gt;Both inputs are attacker-controlled. `ZipFile::size()` returns
`uncompressed_size` verbatim from the central directory, widened to a full `u64`
by a ZIP64 extended-information extra field, and is never cross-checked against
the compressed size, the remaining archive length, or any platform-appropriate
bound for a symlink target. `ZipFile::is_symlink()` is decided entirely by the
`S_IFLNK` bit of the external-attributes field.&lt;/p&gt;
&lt;p&gt;`Vec::with_capacity()` is infallible: when the reservation is refused it calls
`handle_alloc_error()` and aborts the process. This is not a Rust panic. It is
not caught by `catch_unwind()`, is unaffected by `panic = &amp;#34;unwind&amp;#34;`, and is not
contained by running the call on a worker thread.&lt;/p&gt;
&lt;p&gt;A 112-byte archive is sufficient. One `Stored` entry flagged `S_IFLNK` with a
ZIP64 field declaring `uncompressed_size = 2^62` and a zero-byte payload makes
`extract()` fail with:&lt;/p&gt;
&lt;p&gt;```
memory allocation of 4611686018427387904 bytes failed
Aborted (core dumped)          # exit 134
```&lt;/p&gt;
&lt;p&gt;The declared value only needs to exceed the host&amp;#39;s address space, not its RAM:
`Vec::with_capacity()` maps address space without touching pages, so resident
memory stays flat and the abort happens on the refused reservation itself. Under
a `ulimit -v`…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: zip&lt;/p&gt;
&lt;p&gt;`ZipArchive::extract()` sizes the symlink-target buffer from the uncompressed
size declared in the central directory record, before reading a single byte of
entry data:&lt;/p&gt;
&lt;p&gt;```rust
let mut target = Vec::with_capacity(file.size() as usize);
```&lt;/p&gt;
&lt;p&gt;Both inputs are attacker-controlled. `ZipFile::size()` returns
`uncompressed_size` verbatim from the central directory, widened to a full `u64`
by a ZIP64 extended-information extra field, and is never cross-checked against
the compressed size, the remaining archive length, or any platform-appropriate
bound for a symlink target. `ZipFile::is_symlink()` is decided entirely by the
`S_IFLNK` bit of the external-attributes field.&lt;/p&gt;
&lt;p&gt;`Vec::with_capacity()` is infallible: when the reservation is refused it calls
`handle_alloc_error()` and aborts the process. This is not a Rust panic. It is
not caught by `catch_unwind()`, is unaffected by `panic = &amp;#34;unwind&amp;#34;`, and is not
contained by running the call on a worker thread.&lt;/p&gt;
&lt;p&gt;A 112-byte archive is sufficient. One `Stored` entry flagged `S_IFLNK` with a
ZIP64 field declaring `uncompressed_size = 2^62` and a zero-byte payload makes
`extract()` fail with:&lt;/p&gt;
&lt;p&gt;```
memory allocation of 4611686018427387904 bytes failed
Aborted (core dumped)          # exit 134
```&lt;/p&gt;
&lt;p&gt;The declared value only needs to exceed the host&amp;#39;s address space, not its RAM:
`Vec::with_capacity()` maps address space without touching pages, so resident
memory stays flat and the abort happens on the refused reservation itself. Under
a `ulimit -v`…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rustsec-2026-0429</guid>
    </item>
  </channel>
</rss>
