# RUSTSEC-2026-0369: `ZipStreamReader::extract()` applies Unix permissions through extracted symlinks without validating the symlink target stays within the dest

> Attackers can modify file permissions outside the extraction directory via symlink traversal in the zip-rs library, potentially leading to privilege escalation.

- **Severity:** Not scored
- **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:** 10 Oct 2026
- **Also known as:** GHSA-4684-h2q9-2vcp

## What is RUSTSEC-2026-0369?

RUSTSEC-2026-0369 is a path traversal vulnerability in zip, published on 10 Oct 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

`ZipStreamReader::extract()` applies Unix permissions through extracted symlinks without validating the symlink target stays within the destination

For further details see: https://github.com/zip-rs/zip2/security/advisories/GHSA-4684-h2q9-2vcp

## Which versions are affected by RUSTSEC-2026-0369?

1 open source package ship an affected version, including zip.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zip` | crates.io | From 0.0.0-0 | 9.0.0 |

## How do I fix RUSTSEC-2026-0369?

Upgrade zip to 9.0.0 or later.

## Is RUSTSEC-2026-0369 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0369 and fix it if it is affected.

What it is: RUSTSEC-2026-0369 is a path traversal vulnerability in zip, published on 10 Oct 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 RUSTSEC-2026-0369 in the wild and no public exploit code.

Affected packages and fixed versions:
- zip (crates.io): affected from 0.0.0-0; fixed in 9.0.0

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/RUSTSEC-2026-0369/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0369/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0369

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