Quick answers
- Is CVE-2026-115906 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115906 being exploited in the wild.
- How severe is CVE-2026-115906?
- Medium severity, with a CVSS score of 6.5, published 26 October 2026.
- Which products and versions are affected?
- zip (crates.io) >= 0.6.0, < 9.0.0, SEMVER:introduced=0.6.0,fixed=9.0.0; Zip-Rs Zip 0.6.0 to 8.x before 9.0.0.
- Is there a fix for CVE-2026-115906?
- Yes. zip (crates.io): upgrade to 9.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115906 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-115906?
- 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.0 or later
cargo update -p zip
Technical details
The AES entry reader in src/aes.rs only verifies HMAC when an attacker-controlled data counter reaches zero. If the bounded reader reaches end-of-stream while data_remaining is still positive, or if an encrypted entry has no payload, the reader returns clean end-of-stream without comparing the authentication tag. This affects decryption methods by_index_decrypt, by_name_decrypt, by_path_decrypt, and password-enabled by_index_with_options.
Affected products
- zip-rs zip 0.6.0 to 8.x before 9.0.0
Identifiers
- CVE-2026-115906
- GHSA-8hxf-qr8p-62x4
Timeline
- 2026-10-26: disclosed
- 2026-10-09: patched: Version 9.0.0 released