Rust advisories / zip_next
UnmaintainedRUSTSEC-2024-0337 · zip_next
RUSTSEC-2024-0337: The crate `zip_next` has been renamed to `zip`.
Short answerNot a bug report: zip_next is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | zip_next |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2024-04-20 |
| Last changed | 2024-04-24 |
| Also known as | none |
What to do
- Look for a maintained fork or alternative crate.
- If you cannot move yet, acknowledge it in your audit config so CI stays green while you plan: add
"RUSTSEC-2024-0337"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i zip_next.
Details from the advisory
Please switch to the new name. zip_next will receive no further releases.
References
- Package: crates.io/crates/zip_next
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0337.html
- Report: github.com/zip-rs/zip/issues/446
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?