cve.bz

CVE-2026-106070 nodejs node: Business Logic Errors

3.7 lowEPSS 0.4%

Low (3.7) in nodejs node. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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

CVSS 3.0

3.7 low
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-840 Business Logic Errors
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-106070 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106070?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106070?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106070 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nodejs nodefrom 26.12.0 through 26.12.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu24.04:LTS, 26.04:LTS, 26.10 and 5 morenodejsno fix listedUBUNTU-CVE-2026-106070
Alpinev3.23, v3.24nodejs24.22.1-r0ALPINE-CVE-2026-106070
Alpinev3.24nodejs-current26.12.1-r0ALPINE-CVE-2026-106070
Alpaquita25nodejs2626.12.1-r0BELL-CVE-2026-106070
Alpaquitastreamnodejs2626.12.1-r1BELL-CVE-2026-106070
BellSoft Hardened Containers25nodejs2626.12.1-r0BELL-CVE-2026-106070
BellSoft Hardened Containersstreamnodejs2626.12.1-r1BELL-CVE-2026-106070

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This is a Low severity flaw. Red Hat rates it Low because impact is limited to integrity of ZipFile content reads (Integrity Low), exploitation requires a crafted mismatched ZIP and use of the experimental zlib.ZipFile API (high attack complexity), and the feature exists only in Node.js 26.x. Streams that do not ship Node.js 26 are not affected. Memory hardening does not prevent this validation logic error.

Red Hat's mitigation

Avoid the experimental zlib.ZipFile API for security decisions on untrusted archives until Node.js is updated. Validate ZIP archives with a second, independent implementation before trusting extracted content. Do not treat CRC-32 alone as proof of entry integrity for adversarial inputs.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10nodejs22Not affected
Red Hat Enterprise Linux 10nodejs24Not affected
Red Hat Enterprise Linux 10nodejs26Fix deferred
Red Hat Enterprise Linux 8nodejs:22/nodejsNot affected
Red Hat Enterprise Linux 8nodejs:24/nodejsNot affected
Red Hat Enterprise Linux 9nodejs:22/nodejsNot affected
Red Hat Enterprise Linux 9nodejs:24/nodejsNot affected
Red Hat Enterprise Linux 9nodejs:26/nodejsFix deferred
Red Hat Hardened Imageshi/nodejsNot affected
Red Hat Hardened Imagesnodejs20Not affected
Red Hat Hardened Imagesnodejs22Not affected
Red Hat Hardened Imagesnodejs24Not affected
Red Hat Hardened Imagesnodejs25Not affected
Red Hat Hardened Imagesnodejs26Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-106070.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

References

Check your stackJSON