CVE-2026-106070 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

What is CVE-2026-106070?

CVE-2026-106070 is a low-severity vulnerability in nodejs node, published on 23 Oct 2026.

Official 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**.

Weakness: CWE-840

Which versions are affected by CVE-2026-106070?

2 open source packages ship an affected version, including node and node-min.

How do I fix CVE-2026-106070?

Upgrade node to 26.12.1 or later.

Is CVE-2026-106070 being exploited?

There is no known exploitation of CVE-2026-106070 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as ALPINE-CVE-2026-106070, BIT-node-2026-106070, BIT-node-min-2026-106070, GHSA-c2qw-fgxm-vxx4, UBUNTU-CVE-2026-106070.