nodejs · Node.js · published 2026-10-23
CVE-2026-106070
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-106070 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 31% of all CVEs. This Node.js vulnerability: CVSS 3.7 (v3.0). Fixed upstream in Node.js 26.12.1, 24.22.1, 22.23.4; Ubuntu still has unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Node.js 26.12.1, 24.22.1, 22.23.4.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | nodejs | Not affected |
| 12 bookworm | nodejs | Not affected | |
| Ubuntu | 26.04 LTS | nodejs | No fix yet |
| 24.04 LTS | nodejs | No fix yet | |
| Red Hat Enterprise Linux (+3 more packages) | RHEL 9 | nodejs | Not affected |
| RHEL 8 | nodejs | Not affected |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Language runtimeNode.js
Node.js security releases: 26.12.1, 24.22.1, 22.23.4
Upgrade to
26.12.124.22.122.23.4Why: CVE-2026-111497: Known exploited server software, total technical impact.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (31th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 3.7 (v3.0)CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- nodejs node
26.12.0through26.12.0(affected)
Description (from the CVE record)#
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**.
Quoted from the CVE Program record.