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

CVE-2026-123872: node:tls (TLS 1.2 renegotiation, HRR and session resumption SNI handling)

On a TLS server that applies different client-certificate policies per hostname, a client that authenticated for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to a host with a stricter policy. The fix stops renegotiation, HelloRetryRequest and session resumption from changing SNI, and disables resumption for mTLS without a session id context.

Identifier
CVE-2026-123872
Vendor / Product
OpenJS Foundation · Node.js Runtime
Severity / CVSS
HIGH · CVSS 8.1 (CVSS 3.0)
Vector / CWE
CWE-287 (Improper Authentication)
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Affected
Node.js 22.x < 22.23.5, 24.x < 24.22.3, 26.x < 26.13.1
Patched Version
Node.js v22.23.5, v24.22.3, v26.13.1
Priority
P1 — Patch servers with per-hostname client-certificate policies

Executive Summary & Technical Impact

On a TLS server that applies different client-certificate policies per hostname, a client that authenticated for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to a host with a stricter policy. The fix stops renegotiation, HelloRetryRequest and session resumption from changing SNI, and disables resumption for mTLS without a session id context.

Tracked under CVE-2026-123872 (CWE-287 (Improper Authentication)), this vulnerability affects Node.js 22.x < 22.23.5, 24.x < 24.22.3, 26.x < 26.13.1 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.
  2. Audit servers that use SNICallback or server.addContext() with different client CAs per host; give every protected SNI context its own certificate (see CVE-2026-123867).
  3. Where clients allow it, require TLS 1.3 so TLS 1.2 renegotiation is not in play.

Frequently Asked Questions (CVE-2026-123872)

What versions are affected by CVE-2026-123872?

CVE-2026-123872 affects Node.js 22.x < 22.23.5, 24.x < 24.22.3, 26.x < 26.13.1 in Node.js Runtime (node:tls (TLS 1.2 renegotiation, HRR and session resumption SNI handling)).

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

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-123872?

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

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. Rapid7 — CVE-2026-123872