Quick answers
- Is CVE-2026-115905 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115905 being exploited in the wild.
- How severe is CVE-2026-115905?
- Critical severity, with a CVSS score of 4, published 26 October 2026.
- Which products and versions are affected?
- zip (crates.io) <= 9.0.4, SEMVER:introduced=0,fixed=9.0.5; Zip-Rs Zip through 9.0.4.
- Is there a fix for CVE-2026-115905?
- Yes. zip (crates.io): upgrade to 9.0.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115905 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-115905?
- Check whether you run zip (crates.io) or Zip-Rs Zip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- zip (crates.io): upgrade to 9.0.5 or later
cargo update -p zip
Technical details
The vulnerability exists because ZipArchive validates Central Directory File Header filenames while ZipStreamReader extracts using Local File Header filenames without reconciling these duplicate metadata fields in src/read/stream.rs. An attacker can craft a ZIP archive where the central directory lists benign filenames but the local file headers specify different paths, causing the streaming extractor to write to unintended locations and potentially overwrite downstream files.
Affected products
- zip-rs zip through 9.0.4
Identifiers
- CVE-2026-115905
- GHSA-m665-v7pm-7grj
Timeline
- 2026-10-26: disclosed
- 2026-10-17: patched