Node.js patches 16 security flaws, including a high-severity TLS key memory leak
- Severity
- High
- Sources
- 1
What happened
Node.js has fixed 16 flaws across its 22.x, 24.x and 26.x lines, seven rated high, six medium and three low. The high-severity CVE-2026-123864 lets an unauthenticated client leak heap memory, including TLS private keys, from HTTPS servers where a handler calls res.flushHeaders() early and later ends with a non-empty chunk. Other fixes cover HTTP/2 crashes and memory leaks, TLS client certificate bypasses, and proxy credentials appearing in error messages. Trail of Bits and Chris Rohlf were among the reporters, and Matteo Collina fixed most of the issues.
For IT people · Written by AI from 1 source · Wrong?
What to do
- Upgrade Node.js to v22.23.5, v24.22.3 or v26.13.1, starting with public HTTP/2 and HTTPS servers.
- Rebuild container images so they include the new runtime.
- If a vulnerable HTTPS handler served traffic, consider replacing TLS private keys.
Written by AI from the sources, checked against them
Full story timeline · 1 update
Who reported · 1 outlet
Who and what is in it
Companies
Products