<?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://cve.radiocsirt.org</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>Tue, 17 Nov 2026 05:09:48 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-392447</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-392447</link>
      <description>EUVD-2026-392447</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-392447</guid>
    </item>
    <item>
      <title>fkie_cve-2026-115905</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-115905</link>
      <description>&lt;p&gt;zip is a zip library for Rust that supports reading and writing simple ZIP files. Through 9.0.4, ZipArchive treats Central Directory File Header filenames as authoritative while ZipStreamReader extracts using Local File Header filenames without reconciling the duplicate metadata in src/read/stream.rs. A crafted archive can therefore appear benign to a component that inspects the central directory but cause a streaming extractor to write a different attacker-selected path and content, potentially overwriting files used by a downstream service. This issue is fixed in version 9.0.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;zip is a zip library for Rust that supports reading and writing simple ZIP files. Through 9.0.4, ZipArchive treats Central Directory File Header filenames as authoritative while ZipStreamReader extracts using Local File Header filenames without reconciling the duplicate metadata in src/read/stream.rs. A crafted archive can therefore appear benign to a component that inspects the central directory but cause a streaming extractor to write a different attacker-selected path and content, potentially overwriting files used by a downstream service. This issue is fixed in version 9.0.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-115905</guid>
    </item>
    <item>
      <title>GHSA-m665-v7pm-7grj — zip: Critical Parser Differential &amp; Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to A…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m665-v7pm-7grj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: zip&lt;/p&gt;
&lt;p&gt;## Summary
A critical architectural parser differential exists in the `zip` crate (`&amp;lt;= 9.0.4`) between random-access archive readers (`ZipArchive`) and streaming readers (`ZipStreamReader`). `ZipArchive` considers the Central Directory File Header (CDFH) authoritative and ignores the filename declared in the Local File Header (LFH). In contrast, `ZipStreamReader` relies exclusively on the Local File Header (LFH) when extracting files to the filesystem.&lt;/p&gt;
&lt;p&gt;This discrepancy enables ZIP archives to appear to have different file paths and contents according to which tool is reading them.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Architectural Root Cause
In the PKWARE ZIP archive format, every file entry is defined in two distinct locations:
1. **Local File Header (LFH):** Precedes the compressed payload of each file in the body of the archive.
2. **Central Directory File Header (CDFH):** Stored in a contiguous index at the end of the archive.&lt;/p&gt;
&lt;p&gt;In `zip2`:
- `src/read/zip_archive.rs`: `ZipArchive` parses the central directory into `SharedBuilder.files`. All file lookups by index or name read exclusively from the CDFH table, completely ignoring the filename present in the LFH.
- `src/read/stream.rs:L86-L141`: `ZipStreamReader::visit` and `ZipStreamReader::extract` read sequentially from the stream without verifying the central directory index. Each entry is parsed via `read_zipfile_from_stream` and written to disk using the unverified filename declared in the LFH:
  ```rust
  // src/read/stream.rs
  fn…&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;## Summary
A critical architectural parser differential exists in the `zip` crate (`&amp;lt;= 9.0.4`) between random-access archive readers (`ZipArchive`) and streaming readers (`ZipStreamReader`). `ZipArchive` considers the Central Directory File Header (CDFH) authoritative and ignores the filename declared in the Local File Header (LFH). In contrast, `ZipStreamReader` relies exclusively on the Local File Header (LFH) when extracting files to the filesystem.&lt;/p&gt;
&lt;p&gt;This discrepancy enables ZIP archives to appear to have different file paths and contents according to which tool is reading them.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Architectural Root Cause
In the PKWARE ZIP archive format, every file entry is defined in two distinct locations:
1. **Local File Header (LFH):** Precedes the compressed payload of each file in the body of the archive.
2. **Central Directory File Header (CDFH):** Stored in a contiguous index at the end of the archive.&lt;/p&gt;
&lt;p&gt;In `zip2`:
- `src/read/zip_archive.rs`: `ZipArchive` parses the central directory into `SharedBuilder.files`. All file lookups by index or name read exclusively from the CDFH table, completely ignoring the filename present in the LFH.
- `src/read/stream.rs:L86-L141`: `ZipStreamReader::visit` and `ZipStreamReader::extract` read sequentially from the stream without verifying the central directory index. Each entry is parsed via `read_zipfile_from_stream` and written to disk using the unverified filename declared in the LFH:
  ```rust
  // src/read/stream.rs
  fn…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m665-v7pm-7grj</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-115905 — zip: Critical Parser Differential &amp; Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to A…</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-115905</link>
      <description>msrc_CVE-2026-115905</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-115905</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-115905</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-115905</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: rust-zip, Ubuntu:22.04:LTS: rust-zip, Ubuntu:24.04:LTS: rust-zip, Ubuntu:26.10: rust-zip, Ubuntu:26.04:LTS: rust-zip&lt;/p&gt;
&lt;p&gt;zip is a zip library for Rust that supports reading and writing simple ZIP files. Through 9.0.4, ZipArchive treats Central Directory File Header filenames as authoritative while ZipStreamReader extracts using Local File Header filenames without reconciling the duplicate metadata in src/read/stream.rs. A crafted archive can therefore appear benign to a component that inspects the central directory but cause a streaming extractor to write a different attacker-selected path and content, potentially overwriting files used by a downstream service. This issue is fixed in version 9.0.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: rust-zip, Ubuntu:22.04:LTS: rust-zip, Ubuntu:24.04:LTS: rust-zip, Ubuntu:26.10: rust-zip, Ubuntu:26.04:LTS: rust-zip&lt;/p&gt;
&lt;p&gt;zip is a zip library for Rust that supports reading and writing simple ZIP files. Through 9.0.4, ZipArchive treats Central Directory File Header filenames as authoritative while ZipStreamReader extracts using Local File Header filenames without reconciling the duplicate metadata in src/read/stream.rs. A crafted archive can therefore appear benign to a component that inspects the central directory but cause a streaming extractor to write a different attacker-selected path and content, potentially overwriting files used by a downstream service. This issue is fixed in version 9.0.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-115905</guid>
    </item>
  </channel>
</rss>
