# CVE-2026-19693: extract-zip arbitrary file write outside the destination directory via a symlink at the final path component

> Attackers can write arbitrary files outside the destination directory by exploiting symlink handling in extract-zip, potentially leading to code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-19693, GHSA-7pqw-9j4j-h8q3, MINI-228c-c4q8-7jg7, MINI-25cm-7j39-244h, MINI-3v9g-j92w-r22r, MINI-577w-8hfx-p5px, MINI-6frx-wh8f-jhxw, MINI-6pgx-mhf2-8x7g, MINI-g53q-3hff-5jgw, MINI-gq7p-r26g-4xc2, MINI-jvcw-58cj-v83g, MINI-p7r4-gp65-xr2m, MINI-p9hq-rw2p-h9gm, MINI-r6wj-5wwr-wv6w, MINI-wr8h-h2w5-xc3x, MINI-wxrf-237w-rxqg, MINI-x9mp-x4gp-qw37, ROOT-APP-NPM-CVE-2026-19693, UBUNTU-CVE-2026-19693

## What is CVE-2026-19693?

CVE-2026-19693 is a high-severity path traversal vulnerability in max-mapper extract-zip, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

extract-zip through 2.0.1 containment-checks only the parent directory of each archive entry and never the entry's own final path component, so an archive containing two entries with identical names - a symlink whose target is outside the destination, followed by a regular file - writes through the planted symlink and yields an arbitrary file write outside the destination directory.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-19693?

2 open source packages ship an affected version, including extract-zip.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `extract-zip` | npm | All versions to 2.0.1 | None |
| `extract-zip` | npm | All versions to 2.0.1 | None |

## How do I fix CVE-2026-19693?

Upgrade to a fixed version.

## Is CVE-2026-19693 being exploited?

There is no known exploitation of CVE-2026-19693 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19693 and fix it if it is affected.

What it is: CVE-2026-19693 is a high-severity path traversal vulnerability in max-mapper extract-zip, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-19693 in the wild and no public exploit code.

Affected packages and fixed versions:
- extract-zip (npm): affected all versions up to 2.0.1; no fix listed
- extract-zip (npm): affected all versions up to 2.0.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19693/ (Markdown: https://insights.sbomify.com/CVE-2026-19693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19693
- OSV: https://osv.dev/vulnerability/CVE-2026-19693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19693/
Summaries are generated and may contain mistakes; the official description above is the record.