CVE-2026-106070

CVE Enrichment

CVSS: 3.7 LOW
EPSS: 0.37%
EPSS Percentile: 30.53%
CISA KEV: Not listed

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

Technical Details

CVSS Version: 3.0
CNA / NVD Source: [email protected]
Published: 24-Oct-2026 00:17
Last Modified: 24-Oct-2026 02:42
EPSS Date: 2026-10-30
CWE: CWE-840

CVSS Vector


            CVSS:3.0                            AV:N /
                            AC:H /
                            PR:N /
                            UI:N /
                            S:U /
                            C:N /
                            I:L /
                            A:N

References

[email protected]

Last enrichment sync: 31-Oct-2026 13:10
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (1)

CVE-2026-106070 Low zlib (ZipFile) ZIP validation exposes attacker-controlled bytes 26.x Node.js Fixes 10 Vulnerabilities, Including Brotli Remote Code Execution Flaw

CVE (9)

Vendors (1)

Products (7)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.