VulnerabilityPublished 11 Nov 2026

CVE-2026-123874: nodejs node · Use After Free

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:49 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

This vulnerability is fixed in Node.js versions 24.22.3 and 26.13.1. Users should upgrade to these or later versions to remediate the issue. No other mitigation or workaround is indicated by the vendor advisory.

Description

CVE-2026-123874 is a use-after-free vulnerability in Node.js HTTP/2 affecting versions 24.x (since 24.22.0) and 26.x (since 26.9.0). It allows an unauthenticated client to corrupt server memory when the server serves files using respondWithFile() or respondWithFD(). The flaw occurs because the server may free an Http2Stream object while a write request referencing it is still queued, leading to a dereference of a freed object. This vulnerability has a CVSS score of 7.5 and is rated high severity.

Impact

An unauthenticated remote attacker can cause server memory corruption leading to potential denial of service by exploiting the use-after-free in HTTP/2 stream handling during file serving. The vulnerability does not impact confidentiality or integrity but can disrupt service availability.

Summary

This vulnerability in Node.js HTTP/2 arises from a use-after-free condition when serving files with stream.respondWithFile() or stream.respondWithFD(). An unauthenticated client can trigger the server to free an Http2Stream object while a write operation referencing that stream is still pending on the socket. When the write completes, the server dereferences the freed object, causing memory corruption. This affects Node.js versions 24.x from 24.0.0 up to but not including 24.22.3, and 25.x and 26.x from 25.0.0 up to but not including 26.13.1. The vulnerability impacts availability (denial of service) but does not affect confidentiality or integrity. No known exploits are reported in the wild.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats