Node.js zlib.ZipFile returns wrong bytes from mismatched headers
CVE-2026-106070Low
A flaw in Node.js zlib.ZipFile allows an attacker to craft a ZIP archive where the local header does not match the central directory. When the API reads the modified timestamp or content from such an archive, it caches the parsed local header without properly setting the content offset. This causes the API to return bytes from the start of the file instead of the requested entry, whilst CRC-32 verification still passes because the attacker controls the central directory. An attacker needs to create a specially crafted ZIP archive to exploit this, which could cause a Node.js-based scanner to approve different content from what other ZIP implementations would extract.
Plain English summary of the NVD and CISA text, checked by machine against both.
Scores and dates
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Detail
Reports naming this CVE1 in total
· FortiGuard Labs IR Advisories
Multiple Node.js CVEs (opens in a new tab)