Node.js security releases for 22.x, 24.x and 26.x: 16 CVEs, seven of them high severity in HTTP/2 and TLS
Node.js has released security updates for the 22.x, 24.x and 26.x lines. Seven high-severity vulnerabilities concern HTTP/2 and TLS, including remote crashes and memory leaks.
This article was prepared with AI assistance from the official sources listed below, and checked automatically before publication.

The Node.js project, under the OpenJS Foundation, announced a security release on Wednesday, 11 November 2026. Updates are available for three release lines: 26.x, 24.x and 22.x. According to the Node.js announcement page, the release contains 16 CVEs, of which seven are rated high, six medium and three low. Most of the high-severity vulnerabilities are in the HTTP/2 and TLS servers and can be triggered by a remote client without authentication.
High-severity vulnerabilities that have been patched
The following are the high-severity vulnerabilities listed in the Node.js announcement:
- CVE-2026-123863: a reachable assertion on HTTP/2 session closure allows an unauthenticated client to terminate the server process, over either TLS or cleartext. This vulnerability is a variant of CVE-2024-27983 that was not covered by the earlier fix.
- CVE-2026-123864: a zero-length TLS write triggers a re-invocation of
llhttp_execute()on HTTPS. An unauthenticated client can read memory belonging to other connections, including TLS private keys and other users' requests. Node.js states that cleartextnode:httpis not affected. - CVE-2026-123865: a protocol error while an HTTP/2 connection is being closed can cause memory and file descriptors to leak permanently.
- CVE-2026-123866: a use-after-free on HTTP/2 stream closure can send already-freed response memory to the peer.
- CVE-2026-126051: an uncaught exception in a TLS server via a deferred handshake callback, which allows the process to be shut down remotely.
- CVE-2026-123872: TLS 1.2 renegotiation allows a client to change the servername in order to bypass client certificate authentication on protected hosts.
- CVE-2026-123874: a use-after-free in HTTP/2 when the server serves files with
respondWithFile()orrespondWithFD().
In addition, this release updates bundled dependencies: llhttp on 22.x, 24.x and 26.x; undici on 24.x and 26.x; and sqlite on 22.x and 24.x. The first HTTP/2 vulnerability was reported by Chris Rohlf together with Claude and Anthropic Research.
Why this deserves attention
The announcement stresses that several vulnerabilities can be triggered in common configurations. CVE-2026-123863, for example, only requires the built-in http2 server to respond before the request body is complete. The impact covers two areas: service availability, because the process can stop or resources can be exhausted, and data confidentiality, because memory leaks can potentially expose private keys and other users' data.
The authentication vulnerabilities also deserve a closer look. In CVE-2026-123872, the bypass occurs on servers that apply different client certificate policies per hostname. The medium-severity list includes a similar case (CVE-2026-123867) involving per-host mTLS with server.addContext().
Implications for organisations in Indonesia
Node.js is widely used for the backends of public service portals, fintech and e-commerce, often with HTTP/2 or TLS directly facing the internet. Servers like these are at risk if they have not been patched. From a personal data protection perspective, a memory leak that exposes other users' requests should be assessed as a potential data incident under the Personal Data Protection Law (UU PDP). It should be noted that each organisation's level of exposure depends on the version and configuration in use.
Practical steps
- Take an inventory of Node.js versions in production, including container images and runtimes in CI/CD pipelines.
- Schedule an upgrade to the fixed release on the line in use (22.x, 24.x or 26.x), starting with internet-facing services.
- Check where HTTP/2 and TLS/mTLS are terminated, whether in Node.js or in a reverse proxy or load balancer, as this determines the attack surface.
- Review code that uses
respondWithFile(),server.addContext(), SNI or OCSP hooks, and per-hostname client certificate policies. - Monitor for processes that stop suddenly or for abnormal growth in memory and file descriptors as early indicators.
- Prepare incident response procedures, including considering rotation of TLS private keys on servers vulnerable to memory leaks.
The details of the fixed version for each line and the full list of CVEs should be consulted directly in the official Node.js announcement before scheduling updates.
Sources & references
This article is a summary and interpretation by the Oemah Solution team of the sources below. Refer to the original sources for full details and context.

