The Node.js project shipped security releases on 11 November for its three active lines, 22.x, 24.x and 26.x, fixing 16 vulnerabilities: seven rated high, six medium and three low. Most of the high-severity flaws sit in the HTTP/2 and TLS code that internet-facing Node.js servers run every day.

According to the Node.js advisory, CVE-2026-123864 lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users’ requests, on HTTPS servers whose handlers meet specific conditions. Cleartext node:http is not affected. CVE-2026-123863 and CVE-2026-126051 let a remote client terminate the server process, and CVE-2026-123872 lets a client carry its TLS 1.2 client-certificate authentication to a hostname with a stricter policy. The project credits Chris Rohlf, working with Claude and Anthropic Research, for three of the high-severity reports. The releases also update the bundled llhttp, undici and sqlite dependencies.

In our reading, the detail to act on is that two of the high-severity bugs are incomplete fixes: the advisory describes CVE-2026-123863 as a variant of CVE-2024-27983 that the earlier fix did not cover, and CVE-2026-123865 as an incomplete-fix case of CVE-2026-48937. A team that closed those earlier tickets still has open exposure in the same HTTP/2 teardown code. Move to 22.23.5, 24.22.3 or 26.13.1, and check container base images and serverless runtimes that pin an older Node.js version, since those do not pick up the fix on their own. Servers that apply different client-certificate policies per hostname should go first. An exposure inventory decides that first hour, and we argued that the CVE count should not set priorities when Microsoft shipped more than 1,400 CVEs in October.

Source: Node.js: Wednesday, November 11, 2026 Security Releases