Vulnerabilities

Threat intelligence · CVE-2026-115905

zip: Critical Parser Differential & Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to Arbitrary File Overwrite & RCE

Published Oct 26, 2026 · catalog updated Oct 28, 2026 · zip: Critical Parser Differential

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-115905. EPSS is 0.32%. Act only if a listed version of zip: Critical Parser Differential is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (zip: Critical Parser Differential).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical10.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.32%
Remediation
Version ranges on file
Affected products
crates.io zip · rust zip · vendor zip-rs zip2

## Summary A critical architectural parser differential exists in the crate ( ) between random-access archive readers ( ) and streaming readers ( ). considers the Central Directory File Header (CDFH) authoritative and ignores the filename declared in the Local File Header (LFH). In contrast, relies exclusively on the Local File Header (LFH) when extracting files to the filesystem. This discrepancy enables ZIP archives to appear to have different file paths and contents according to which tool is reading them. --- ## Details ### 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. In : - : parses the central directory into . All file lookups by index or name read exclusively from the CDFH table, completely ignoring the filename present in the LFH. - : and read sequentially from the stream without verifying the central directory index. Each entry is parsed via and written to disk using the unverified filename declared in the LFH: - : The crate explicitly exposes , an API that constructs dual-header desynchronizations by adding a new CDFH entry with an alias name pointing to an existing file without updating the original LFH. ### Threat Scenario & Severity Justification (10.0 / 9.9 Critical) 1. **Security Control Evasion:** An adversary crafts a ZIP archive where: - Central Directory Header declares: (Clean document) - Local File Header declares: (Malicious root backdoor) 2. The archive is uploaded through a web portal or API endpoint protected by security gateways (WAF, Anti-Virus, Content Disarm & Reconstruction). The security gateway inspects the archive using (or similar CDFH-first parsers), detects only , and approves the file. 3. The backend worker or cloud function receives the approved archive and e

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • crates.io zip0 → 9.0.5
  • rust zip<= 9.0.4
  • vendor zip-rs zip2version unspecified

How to fix CVE-2026-115905

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-115905. EPSS is 0.32%. Act only if a listed version of zip: Critical Parser Differential is installed.

Which versions are affected?

Compare what you have installed with 0 → 9.0.5, <= 9.0.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-20: Improper Input Validation; CWE-436. EPSS 0.32%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 28, 2026 · GitHub Advisory Database

    Detected

    ## Summary A critical architectural parser differential exists in the crate ( ) between random-access archive readers ( ) and streaming readers ( ). considers the Central Directory File Header (CDFH) authoritative and ignores the filename declared in the Local File Header (LFH). In contrast, relies exclusively on the Local File Header (LFH) when extracting files to the filesystem. This discrepancy

  2. Oct 28, 2026 · GitHub Advisory Database

    Fix available

    zip fixed in 9.0.5

  3. Oct 28, 2026 · GitHub Advisory Database

    Fix available

    zip fixed in 9.0.5

  4. Oct 28, 2026 · GitHub Advisory Database

    Updated

    ## Summary A critical architectural parser differential exists in the crate ( ) between random-access archive readers ( ) and streaming readers ( ). considers the Central Directory File Header (CDFH) authoritative and ignores the filename declared in the Local File Header (LFH). In contrast, relies exclusively on the Local File Header (LFH) when extracting files to the filesystem. This discrepancy

Sources

  • CVE.orgVulnerability recordCVE-2026-115905

    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

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-m665-v7pm-7grj

    zip: Critical Parser Differential & Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to Arbitrary File Overwrite & RCE

    github.com
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-m665-v7pm-7grj

    zip: Critical Parser Differential & Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to Arbitrary File Overwrite & RCE

    osv.dev

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgOct 29, 2026
  • GitHub Advisory DatabaseOct 29, 2026
  • OpenSSF OSV / OSV ScannerOct 29, 2026