VulnerabilityPublished 11 Nov 2026

CVE-2026-126051: nodejs node · NULL Pointer Dereference

Affects nodejs nodeSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 26.13.1 or 24.22.3 soon.

Data as of 11 Nov 2026, 18:50 UTC

CVSS 3.0 base score

7.5High

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (openjs)	CVSS 3.0	7.5

Patch: Available – fixed in 26.13.1, 24.22.3

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

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

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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 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 11 Nov 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 nodejs node to 26.13.1 or 24.22.3.

Affected software

Product	Affected	Fixed in
nodejsnode	Affected >=25.0.0 <26.13.1	Fixed in 26.13.1
nodejsnode	Affected >=24.0.0 <24.22.3	Fixed in 24.22.3

AI-suggested

Upgrade Node.js to versions 24.22.3 or later in the 24.x line, or 26.13.1 or later in the 26.x line, where this issue is fixed. No other mitigation is indicated by the vendor advisory.

Description

CVE-2026-126051 is a high-severity vulnerability in Node.js versions 24.x and 26.x involving a NULL pointer dereference during TLS server handshake. It occurs when certain OpenSSL callbacks are deferred but the underlying socket is destroyed before the callback executes, causing the Node.js process to terminate unexpectedly. This can be triggered remotely by an unauthenticated attacker sending a crafted client hello message. Fixed versions are 24.22.3 and 26.13.1.

Impact

A remote, unauthenticated attacker can cause the Node.js server process to terminate unexpectedly, resulting in a denial of service. There is no impact on confidentiality or integrity, but availability is severely affected due to process termination.

Summary

This vulnerability arises from a deferred-callback use-after-destroy flaw in Node.js TLS server handshake handling. When a TLS server uses hooks such as SNICallback, OCSPRequest, newSession, resumeSession, or server.addContext(), the corresponding OpenSSL callbacks are deferred. If the underlying socket is destroyed between scheduling and execution of these callbacks, the process raises an uncaught exception instead of emitting an 'error' event, leading to a server crash. An attacker can exploit this by sending a client hello that triggers the vulnerable code path (e.g., no SNI with an OCSP request) followed by padding and a socket FIN, causing the socket to be destroyed before the deferred callback runs. This affects Node.js versions >=24.0.0 <24.22.3 and >=25.0.0 <26.13.1. The issue is fixed in Node.js 24.22.3 and 26.13.1.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 18:50 UTC

Technical details

References

Community reviews

Related threats