Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0297 json

`unzip`: archive extraction is vulnerable to path traversal (zip-slip)

published 2mo ago modified last mo.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Summary

`Unzipper::unzip` extracts each archive entry to a path built from the entry's **raw, attacker-controlled name** without any traversal check. A ZIP archive whose entry names contain `../` components (or an absolute path) can therefore cause files to be written **outside** the destination directory chosen by the caller — a "zip-slip" / directory-traversal arbitrary file write (CWE-22 / CWE-23 / CWE-36).

### Affected versions

All published versions are affected. `unzip` has only ever released `0.1.0` (published 2017-12-23) and appears unmaintained, so **no fixed version is available**.

### Proof of concept

A malicious archive with a single entry named `../ESCAPED.txt` extracted via `Unzipper::unzip` writes `ESCAPED.txt` one level above the destination directory.

Is RUSTSEC-2026-0297 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io unzip
>=0.0.0-0
 no fix listed

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.