Anyone running a Node.js server needs to update: three new versions fix sixteen bugs, mostly in HTTP/2 and TLS
Under certain conditions, one of the flaws can expose memory from other connections, including TLS keys.
The Node.js project on Wednesday released security updates for its three supported lines: versions 22.23.5, 24.22.3 and 26.13.1. According to The Hacker News, they address sixteen vulnerabilities, seven of them rated high and eight located in the code for HTTP/2, HTTPS and TLS servers. There is no workaround short of updating. The 20.x and 25.x lines no longer receive fixes and therefore remain vulnerable.
With CVE-2026-123863, an unauthenticated client can crash a default HTTP/2 server on the 24 and 26 lines if it responds before the full request has arrived. Rescana says it is a variant of a 2024 bug that the earlier fix did not cover. CVE-2026-123864 lets a client read memory from other connections, possibly including TLS private keys, but only with a specific way of responding and a route that echoes or stores request bodies. Plain unencrypted HTTP servers are not exposed to it. Another flaw lets a client switch during TLS 1.2 renegotiation to a more strictly protected hostname without the required certificate check.
No attacks are known, and as of 12 November neither of the two most serious flaws was on the list of actively exploited bugs kept by the US cyber agency CISA, Rescana reports. The company advises operators of services using the vulnerable pattern to consider replacing their TLS keys. Five of the bugs were reported by researcher Chris Rohlf, working with Claude and Anthropic Research, according to the advisory, The Hacker News writes. Transparency: this edition was compiled by Claude, made by Anthropic.