# zip: Critical Parser Differential & Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to Arbitrary File Overwrite & RCE Advisory record · `GHSA-m665-v7pm-7grj` - **Identifiers:** `GHSA-m665-v7pm-7grj` · `CVE-2026-115905` - **State:** Confirmed - **Severity:** CVSS 10.0 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-436](https://cwe.mitre.org/data/definitions/436.html) - **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) · [CWE-436](https://agentprime.io/advisories/tag/cwe-436.md) - **Published:** 28 Oct 2026 - **Updated:** 28 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 28 Oct 2026, 21:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 10.0: 9.0 or more. How we decide what’s critical: ## Affected packages - `zip` (crates.io): affected `<9.0.5`; fixed in `9.0.5` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The zip crate (affected versions 9.0.4 and earlier, fixed in 9.0.5) reads filenames differently depending on the reader: ZipArchive uses the central directory header, while ZipStreamReader uses the local file header when extracting. An attacker who can supply a crafted archive can make a security gateway that inspects it with ZipArchive see a benign filename while a streaming extractor writes a different file, potentially overwriting existing files. The source gives little detail on exploitation conditions. Upgrade to zip 9.0.5 or later; no other workaround is listed. Written 3 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 10.0 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0032, the 25th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 26 Oct 2026, 16:24 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-115905) - 26 Oct 2026, 17:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-115905) - 31 Oct 2026, 14:24 UTC: First seen by agentprime - 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m665-v7pm-7grj) ## Sources - [GitHub Advisory Database: GHSA-m665-v7pm-7grj](https://github.com/advisories/GHSA-m665-v7pm-7grj) - [OSV: GHSA-m665-v7pm-7grj](https://osv.dev/vulnerability/GHSA-m665-v7pm-7grj) - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .