Node.js Fixes 16 Flaws, Including HTTP/2 Bugs That Crash Servers and Leak Other Connections' Data
Our summary
Node.js maintainers shipped fixes for 16 vulnerabilities across the 22.x, 24.x and 26.x release lines, patched in versions 22.23.5, 24.22.3 and 26.13.1. Seven of the bugs are rated high severity, led by CVE-2026-123863, which lets an unauthenticated client crash a default HTTP/2 server simply by sending a reply before the request body fully arrives. Equally serious is CVE-2026-123864, affecting HTTPS servers that call res.flushHeaders() early, which can expose memory from unrelated connections, including TLS private keys and other users' request data. A related flaw, CVE-2026-123866, lets attackers force a server to leak pieces of other connections' responses over HTTP/2. Additional high-severity issues—CVE-2026-123865, CVE-2026-123874, CVE-2026-126051 and CVE-2026-123872—allow resource exhaustion, memory corruption during file transfers, TLS server crashes via certain callback hooks, and bypass of stricter per-hostname client-certificate requirements during TLS 1.2 renegotiation. All affected code lives in Node.js's built-in HTTP/2, HTTPS and TLS server implementations, so exposure depends on whether an application terminates these protocols directly in Node.js. The project has not disclosed any in-the-wild exploitation and offers no workaround beyond upgrading, while end-of-life branches such as 20.x and 25.x remain permanently vulnerable. Researcher Chris Rohlf, working with Claude and Anthropic Research, is credited with reporting five of the flaws, including the two most severe ones.
The Hacker News publishes this story on its own site; we link to it rather than reprint it.
Worried this affects your company?
Discuss a security assessment of your internet-facing systems. Scope agreed before testing.