GHSA-p634-w6r4-rjp2: adm-zip: Duplicate ZIP entry names: getEntry() and extractAllTo() resolve to different content
Summary A ZIP file can contain two entries with the identical name. adm-zip keeps both in its internal entry list, but its name-lookup table only retains the last one written. getEntry(name) and extractAllTo() walk these two different internal structures, so they can each resolve a duplicate name to a different entry.
Published Sep 29, 2026
Affected packages
adm-zip
- Ecosystem
- npm
- Affected
- <= 0.6.0
- Fixed in
- 0.6.1
- Check
npm ls adm-zip
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A ZIP file can contain two entries with the identical name. adm-zip keeps both in its internal entry list, but its name-lookup table only retains the last one written. getEntry(name) and extractAllTo() walk these two different internal structures, so they can each resolve a duplicate name to a *different* entry. An application that validates a named entry's contents via getEntry() before trusting an archive, then extracts the whole archive, can end up approving one file's content while a different file's bytes are what actually land on disk under that name.
Details
zipFile.js:58-83retains both entries inentryListbut overwritesentryTable[name]with only the last one written.adm-zip.js:83-95,658-663usesentryTableforgetEntry()lookups — returns the *last* duplicate.adm-zip.js:769-914iteratesentryListfor extraction — writes the *first* duplicate (sync, default overwrite policy).
PoC
const AdmZip = require('adm-zip');
const z = new AdmZip({ noSort: true });
z.addFile('a.txt', Buffer.from('FIRST'));
z.addFile('b.txt', Buffer.from('SECOND'));
const raw = Buffer.from(z.toBuffer());
// rename the a.txt entry to b.txt directly in the raw bytes
for (let at = raw.indexOf('a.txt'); at >= 0; at = raw.indexOf('a.txt', at + 5)) {
raw.write('b.txt', at);
}
const parsed = new AdmZip(raw, { noSort: true });
const validated = parsed.getEntry('b.txt').getData().toString();
parsed.extractAllTo(outDir, false);
// validated === "SECOND", but the file written to disk === "FIRST"Reproduced on the pinned commit (2b4d84087d45344643e0183756e19191d52815cc)
Impact
An application that checks a named entry's content before trusting an untrusted ZIP, then extracts it, can be made to approve different bytes than what actually gets written to disk — the classic check/use split that this kind of validate-then-extract pattern relies on.
Credited to zikk090.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-102282
adm-zip extraction preserves SUID/SGID bits from untrusted ZIPs -> local privilege escalation
high7.1Sep 29, 2026GHSA-8238-w5pm-2374
adm-zip: Unhandled error event in async DEFLATE decompression crashes Node.js process (DoS)
high7.5Sep 29, 2026GHSA-c6fg-446q-cg94
adm-zip: getDataAsync() bypasses the maxOutputLength size guard enforced by the synchronous getData() path
medium5.3Sep 29, 2026GHSA-rcw4-f5rp-g42v
adm-zip: Decompression-bomb protection (fix for CVE-2026-39244) can be bypassed by declaring uncompressed size as 0
high7.5Sep 29, 2026CVE-2026-77301
adm-zip: Uncontrolled memory allocation via the declared uncompressed size (DoS)
high7.5Sep 18, 2026CVE-2026-76845
adm-zip extraction follows destination symlinks, allowing arbitrary file overwrite
medium6.5No fixAug 24, 2026
