Node.js patches 16 security flaws, including a high-severity TLS key memory leak
- Severity
- High
- Sources
- 1
What happened
Node.js 22.23.5, 24.22.3 and 26.13.1 fix 16 CVEs (seven high, six medium, three low), and also refresh llhttp, undici and sqlite. CVE-2026-123864 (high, all lines) is a zero-length TLS write that re-enters llhttp during body parsing, causing use-after-free and heap disclosure, including TLS private keys; exposure requires res.flushHeaders() followed by a non-empty chunk, and plain node:http is unaffected. Other highs include CVE-2026-123863 (incomplete fix for CVE-2024-27983), CVE-2026-123874 and CVE-2026-123872 (TLS 1.2 renegotiation servername change bypassing client certificate checks). Prioritise public HTTP/2 and HTTPS servers, rebuild container images, and consider rotating TLS keys where a vulnerable handler was exposed.
For security analysts · 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