Skip to main content
VulnerabilityPublished

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

Affects nodejs nodeSource CVE Database V5

0
Compare

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

Data as of 11 Nov 2026, 18:35 UTC

CVSS 3.0 base score
8.1High
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.08.1
Patch
Available – fixed in 26.13.1, 24.22.3, 22.23.5
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/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

This vulnerability is fixed in Node.js versions 22.23.5, 24.22.3, and 26.13.1. Users should upgrade affected Node.js versions to these or later releases to remediate the issue. No alternative mitigations are indicated. Since this is not a cloud service, patching the Node.js runtime is required.

Description

CVE-2026-123864 is a use-after-free vulnerability in Node.js HTTPS that allows an unauthenticated client to read memory from other connections, including sensitive data such as TLS private keys and other users' requests. The flaw arises from a re-entrancy issue during TLS record processing triggered by specific HTTP handler behaviors involving res.flushHeaders() and res.end(). It affects Node.js versions 22.x, 24.x, and 26.x prior to the fixed releases.

References

Community reviews

Loading reviews…