CVE-2026-123864 HIGH · CVSS 8.1 (CVSS 3.0) · OpenJS Foundation — Node.js Runtime ·

CVE-2026-123864: HTTPS server (TLSWrap / llhttp request parser)

A zero-length TLS write issued from inside the HTTP parser on_body callback makes TLSWrap::DoWrite() call ClearOut() directly, re-entering llhttp_execute() mid-body. The resulting use-after-free and out-of-bounds heap read lets an unauthenticated client get freed or unrelated heap memory, including other connections' requests and TLS private keys, copied into a request body. Requires a handler that calls res.flushHeaders() before the body ends and later res.end() with a non-empty chunk, plus a route that echoes or stores request bodies.

Identifier
CVE-2026-123864
Vendor / Product
OpenJS Foundation · Node.js Runtime
Severity / CVSS
HIGH · CVSS 8.1 (CVSS 3.0)
Vector / CWE
CWE-416 (Use After Free) / CWE-125 (Out-of-bounds Read)
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
Affected
Node.js 22.x < 22.23.5, 24.x < 24.22.3, 26.x < 26.13.1 (cleartext node:http not affected)
Patched Version
Node.js v22.23.5, v24.22.3, v26.13.1
Priority
P1 — Patch HTTPS-terminating Node services this week

Executive Summary & Technical Impact

A zero-length TLS write issued from inside the HTTP parser on_body callback makes TLSWrap::DoWrite() call ClearOut() directly, re-entering llhttp_execute() mid-body. The resulting use-after-free and out-of-bounds heap read lets an unauthenticated client get freed or unrelated heap memory, including other connections' requests and TLS private keys, copied into a request body. Requires a handler that calls res.flushHeaders() before the body ends and later res.end() with a non-empty chunk, plus a route that echoes or stores request bodies.

Tracked under CVE-2026-123864 (CWE-416 (Use After Free) / CWE-125 (Out-of-bounds Read)), this vulnerability affects Node.js 22.x < 22.23.5, 24.x < 24.22.3, 26.x < 26.13.1 (cleartext node:http not affected) and carries a severity score of 8.1 (CVSS 3.0) (HIGH). Engineering and security operations teams running Node.js Runtime should prioritize upgrading to Node.js v22.23.5, v24.22.3, v26.13.1.

Remediation & Patch Guidance

  1. Upgrade to Node.js v22.23.5, v24.22.3 or v26.13.1 and rebuild container images that pin a Node patch version.
  2. Prioritize services that terminate HTTPS directly in Node and echo or persist request bodies.
  3. If patching is delayed, terminate TLS at a reverse proxy or load balancer in front of Node.

Frequently Asked Questions (CVE-2026-123864)

What versions are affected by CVE-2026-123864?

CVE-2026-123864 affects Node.js 22.x < 22.23.5, 24.x < 24.22.3, 26.x < 26.13.1 (cleartext node:http not affected) in Node.js Runtime (HTTPS server (TLSWrap / llhttp request parser)).

How do I patch or remediate CVE-2026-123864?

Upgrade affected deployments to Node.js v22.23.5, v24.22.3, v26.13.1 and verify the remediation steps listed above.

What is the CVSS score of CVE-2026-123864?

CVE-2026-123864 is rated HIGH with a CVSS score of 8.1 (CVSS 3.0) (vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H).

Full TechPulse Investigation

Node.js November 2026 Security Release: an HTTPS Heap Leak, an mTLS Bypass and a Pile of HTTP/2 Crashes

Node.js 22.23.5, 24.22.3 and 26.13.1 fix 17 CVEs, seven of them rated high. The worst lets a client read other connections' memory, including TLS private keys, from an HTTPS server. Several were found by Anthropic Research working with Claude.

Read full engineering post-mortem (6 min read) →

Official Vendor & NVD Advisory Links

  1. Node.js — November 11, 2026 Security Releases
  2. NVD — CVE-2026-123864