CVE-2026-106070VulnerabilityPublished 29 Oct 2026

node

Affects nodeSource GCVE Database

Compare

Authoritative record:CVE-2026-106070· Low 3.7

Not known to be exploited · CVSS 3.7 Low : upgrade to 26.12.1 when convenient.

Data as of 29 Oct 2026, 13:19 UTC

CVSS 3.0 base score

3.7Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (hackerone)	CVSS 3.0	3.7

Patch: Available – fixed in 26.12.1

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade node to 26.12.1.

Affected software

Product	Affected	Fixed in
Bitnaminode`pkg:bitnami/node`Other threats	Affected >=25.0.0 <26.12.1	Fixed in 26.12.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and fixed the vulnerability in Node.js version 26.12.1. Users should upgrade to Node.js 26.12.1 or later to remediate this issue.

Description

A vulnerability in the Node.js zlib.ZipFile API allows it to return bytes not belonging to the requested ZIP entry when local and central header validation fails. This occurs because the parsed local header is cached without a content offset, causing subsequent reads to return attacker-controlled bytes from the start of the file. The CRC-32 check still passes due to attacker control of the central directory CRC. This can cause Node.js-based ZIP scanners to approve different content than other ZIP implementations extract. The flaw affects Node.js versions 25.0.0 up to but not including 26.12.1 and is fixed in 26.12.1.

Impact

An attacker can craft a ZIP archive that causes Node.js zlib.ZipFile API to return incorrect content bytes while passing CRC-32 verification. This may lead to Node.js-based scanners approving manipulated content that differs from what other ZIP implementations extract. The impact is limited to content validation discrepancies and does not indicate remote code execution or privilege escalation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 13:19 UTC

Public exploits and detectionGitHub proofs of concept

Technical details

References

Community reviews

Related threats