zip
Affected
- introduced
0.0.0-0, fixed9.0.5(semver)
Fixed versions
9.0.5
Fix
- Fixed version
9.0.5cargo update -p zip --precise 9.0.5
Advisory
Also known as: CVE-2026-115905, GHSA-m665-v7pm-7grj
ZipStreamReader extracts entries under local-header names that can differ from the central directory
A ZIP archive names each entry twice: in the local file header in front of the entry's data, and in the central directory at the end of the archive. ZipArchive lists and opens entries by their central-directory names. ZipStreamReader::visit and ZipStreamReader::extract, like read_zipfile_from_stream, read the local headers in order and use the local-header names without comparing them with the central directory.
An archive can therefore show one set of file names to code that inspects it with ZipArchive and write files under other names when it is extracted with ZipStreamReader. If an application checks an archive one way and extracts it the other way, an attacker can get files written or overwritten inside the destination directory that the check never saw.
The fix adds an opt-in check. ZipStreamReader::enforce_header_consistency(true) compares each local header with its central-directory entry (name, sizes, CRC-32, compression method, flags and modification time) and fails extraction on a mismatch; ZipReadOptions::enforce_header_consistency(true) and ZipArchive::validate_header_consistency() do the same for ZipArchive. The check is off by default, so upgrading alone does not change what ZipStreamReader::new(...) extracts: applications that extract untrusted archives with ZipStreamReader need to turn it on.
Not rated by the source.
0.0.0-0, fixed 9.0.5 (semver)9.0.5
9.0.5cargo update -p zip --precise 9.0.5Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0