CVE-2026-123877: CVE-2026-123877 (Node.js November 2026 Security Release)
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.
Executive Summary & Technical Impact
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.
Tracked under CVE-2026-123877 (CWE-Other (Security Advisory)), this vulnerability affects Node.js 22.x < 22.23.5, 24.x < 24.22.3, 26.x < 26.13.1; end-of-life lines are also affected and carries a severity score of 8.1 (HIGH). Engineering and security operations teams running Node.js Infrastructure should prioritize upgrading to 22.23.5, 24.22.3, 26.13.1.
Remediation & Patch Guidance
- The Node.js project shipped security releases for all three supported lines on November 11, 2026: v22.23.5, v24.22.3 and v26.13.1. The highest severity is HIGH; there's no critical this time.
- CVE-2026-123864 (CVSS 8.1): a zero-length TLS write from inside the HTTP parser's body callback re-enters llhttp, and the HTTPS server can copy freed heap memory, including other users' requests and TLS private keys, into a request body. Cleartext node:http is not affected.
- CVE-2026-123872 (CVSS 8.1): a TLS 1.2 client can change the servername during renegotiation and carry its client-cert authentication to a stricter host. A related medium bug (CVE-2026-123867) makes CA-only SNI contexts fall back to the default client CA.
- Most of the rest are remote HTTP/2 crashes, leaks and use-after-frees, several reachable on default servers. If you run HTTP/2 or HTTPS directly on Node, upgrade now.
Frequently Asked Questions (CVE-2026-123877)
What versions are affected by CVE-2026-123877?
CVE-2026-123877 affects Node.js 22.x < 22.23.5, 24.x < 24.22.3, 26.x < 26.13.1; end-of-life lines are also affected in Node.js Infrastructure (CVE-2026-123877 (Node.js November 2026 Security Release)).
How do I patch or remediate CVE-2026-123877?
Upgrade affected deployments to 22.23.5, 24.22.3, 26.13.1 and verify the remediation steps listed above.
What is the CVSS score of CVE-2026-123877?
CVE-2026-123877 is rated HIGH with a CVSS score of 8.1 (vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
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) →