# zip: Arbitrary file write outside the extraction directory, because ZipArchive::extract validates symlink targets lexically.

Advisory record · `GHSA-hjqx-j4rw-g7xv`

- **Identifiers:** `GHSA-hjqx-j4rw-g7xv` · `CVE-2026-115908`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-59](https://cwe.mitre.org/data/definitions/59.html) · [CWE-61](https://cwe.mitre.org/data/definitions/61.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [CWE-61](https://agentprime.io/advisories/tag/cwe-61.md)
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Oct 2026, 16:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `zip` (crates.io): affected `>=7.2.0, <9.0.0`; fixed in `9.0.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The zip crate from 7.2.0 before 9.0.0 can write files outside the extraction directory through ZipArchive::extract. An attacker who supplies a crafted archive with symlinks, and who knows or can guess the absolute destination path, can write arbitrary files outside that directory. Upgrade to zip 9.0.0 or later.

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

- 7.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 37th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hjqx-j4rw-g7xv)

## Sources

- [GitHub Advisory Database: GHSA-hjqx-j4rw-g7xv](https://github.com/advisories/GHSA-hjqx-j4rw-g7xv)
- [OSV: GHSA-hjqx-j4rw-g7xv](https://osv.dev/vulnerability/GHSA-hjqx-j4rw-g7xv)
- <https://github.com/zip-rs/zip2/security/advisories/GHSA-hjqx-j4rw-g7xv>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-115908>
- <https://github.com/zip-rs/zip2/commit/09c030eab56e8db8fb3c1c33f554407b30bad8fa>
- <https://github.com/zip-rs/zip2>
- <https://github.com/zip-rs/zip2/releases/tag/v9.0.0>

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 (<https://api.agentprime.io/mcp>), 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: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hjqx-j4rw-g7xv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hjqx-j4rw-g7xv/>. Everything for agents: <https://agentprime.io/llms.txt>.