Skip to main content
VulnerabilityPublished

CVE-2026-123865: nodejs node · Uncontrolled Resource Consumption

Affects nodejs nodeSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 7.5 High · fixed in 26.13.1 : patch nodejs node soon.

Data as of 11 Nov 2026, 18:35 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.07.5
Patch
Available – fixed in 26.13.1, 24.22.3, 22.23.5
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade nodejs node to 26.13.1, 24.22.3 or 22.23.5.

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=25.0.0 <26.13.1
Fixed in
  • 26.13.1
nodejsnodeAffected
  • >=23.0.0 <24.22.3
Fixed in
  • 24.22.3
nodejsnodeAffected
  • <22.23.5
Fixed in
  • 22.23.5

AI-suggested

Fixed versions are available: Node.js 22.23.5, 24.22.3, and 26.13.1. Users should upgrade to these or later versions to remediate the vulnerability. No other mitigations are indicated by the vendor advisory.

Description

CVE-2026-123865 is a high-severity vulnerability in Node.js HTTP/2 implementation affecting versions 22.x, 24.x, and 26.x prior to fixed releases. An unauthenticated HTTP/2 client can cause permanent memory and file descriptor leaks by triggering protocol errors during session shutdown, leaving connections in CLOSE_WAIT state and consuming server resources indefinitely.

References

Community reviews

Loading reviews…