Node.js patches multiple HTTP/2, TLS vulnerabilities
NCSC-NL advisory details multiple Node.js vulnerabilities in HTTP/2, HTTPS, and TLS handling, fixed in versions 22.23.0, 24.17.0/24.18.0 and 26.x.
Sourceadvisories.ncsc.nl — open the original
What to check
- Applies to
- The 16 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
NCSC-NL published an advisory covering a batch of vulnerabilities patched in Node.js versions 22.x, 24.x and 26.x. The flaws span the HTTP/2 implementation, HTTPS server module, TLS handling, and proxy error handling, and include heap-based buffer overflow, use-after-free, NULL pointer dereference, out-of-bounds write, improper certificate validation, and information disclosure issues. Impacts range from server crashes and memory corruption to leakage of sensitive data including TLS private keys, bypass of client-certificate authentication under TLS 1.2, incorrect TLS session reuse across differing certificate configurations, credential leakage via proxy authentication error messages, and a file-watching access-control bypass on macOS and Windows.
Environments that terminate TLS/HTTPS or expose HTTP/2 endpoints in Node.js are most at risk, since several of the higher-severity issues (CVSS up to 8.2) directly affect those code paths. No active exploitation is mentioned in the advisory. Defenders running Node.js should upgrade to the patched releases (22.23.0, 24.17.0/24.18.0, or the fixed 26.x line) and review the referenced CVEs for applicability to their deployment, prioritising services exposing HTTPS/TLS and HTTP/2 to untrusted networks.
Mentioned in this report
Source reporting: https://advisories.ncsc.nl/2026/ncsc-2026-0492.html
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,433 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs