Vulnerability 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**.
CVSS Score
LOW
Related Weaknesses (CWE)
References
FAQ
What is CVE-2026-106070?
CVE-2026-106070 is a vulnerability with a CVSS score of 3.7 (LOW). 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 o...
How severe is CVE-2026-106070?
CVE-2026-106070 has been rated LOW with a CVSS base score of 3.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-106070?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.