CVE-2026-106070

Published: October 24, 2026Last modified: November 1, 2026

Description

A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails. When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive. This vulnerability affects Node.js **26.x**.

Severity score breakdown

ParameterValue
Base score3.7
Attack VectorNETWORK
Attack complexityHIGH
Privileges requiredNONE
User interactionNONE
ScopeUNCHANGED
ConfidentialityNONE
Integrity impactLOW
Availability impactNONE
VectorCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Status

ProductReleasePackageStatus
Alpaquita Linux23 LTSnodejsUnknown (18.16.0-r0)
25 LTSnodejsUnknown (22.16.0-r1)
nodejs22Unknown (22.23.2-r1)
nodejs24Unknown (24.18.1-r0)
nodejs26Fixed (26.12.1-r0)
StreamnodejsUnknown (18.16.1-r0)
nodejs22Unknown (22.23.2-r0)
nodejs24Unknown (24.18.1-r3)
nodejs26Fixed (26.12.1-r1)
Hardened Containers23 LTSnodejsUnknown (18.16.0-r0)
25 LTSnodejsUnknown (22.16.0-r1)
nodejs22Unknown (22.23.2-r1)
nodejs24Unknown (24.18.1-r0)
nodejs26Fixed (26.12.1-r0)
StreamnodejsUnknown (18.16.1-r0)
nodejs22Unknown (22.23.2-r0)
nodejs24Unknown (24.18.1-r3)
nodejs26Fixed (26.12.1-r1)

References

ON THIS PAGE