Threat Advisory

Remote Attackers Can Read Node.js TLS Private Keys and Crash Servers

Threat: Vulnerability
Targeted Region: Global
Targeted Sector: Technology & IT
Criticality: High
[subscribe_to_unlock_form]

EXECUTIVE SUMMARY:

Multiple security vulnerabilities have been identified in Node.js, affecting the 22.x, 24.x, and 26.x release lines. These flaws impact critical components including the HTTPS implementation, HTTP/2 handling, and TLS session management. The overall risk is significant, as the issues allow for remote denial of service, memory corruption, and the exposure of sensitive data such as private keys and credentials. The combination of high-severity memory leaks and protocol bypasses poses a substantial threat to public-facing servers.

CVE-2026-123864: A high-severity memory leak in the HTTPS code allows an unauthenticated client to read memory belonging to other connections. This flaw is triggered by a re-entry issue during zero-length TLS writes, which can expose TLS private keys and other users' request data.[/subscribe_to_unlock_form]

EXECUTIVE SUMMARY:

Multiple security vulnerabilities have been identified in Node.js, affecting the 22.x, 24.x, and 26.x release lines. These flaws impact critical components including the HTTPS implementation, HTTP/2 handling, and TLS session management. The overall risk is significant, as the issues allow for remote denial of service, memory corruption, and the exposure of sensitive data such as private keys and credentials. The combination of high-severity memory leaks and protocol bypasses poses a substantial threat to public-facing servers.

CVE-2026-123864: A high-severity memory leak in the HTTPS code allows an unauthenticated client to read memory belonging to other connections. This flaw is triggered by a re-entry issue during zero-length TLS writes, which can expose TLS private keys and other users' request data.[emaillocker id="1283"]

CVE-2026-123863: A high-severity flaw in the HTTP/2 implementation allows any client to abort a default server. This issue is a variant of a previously fixed vulnerability that was missed by the earlier patch, leading to a session teardown assertion failure.

CVE-2024-27983: This vulnerability is referenced as the original issue that the fix for CVE-2026-123863 addresses, representing a prior HTTP/2 session teardown flaw that was not fully resolved in the older update.

CVE-2026-123874: A high-severity use-after-free vulnerability affects servers that send files using the respondWithFile method. The flaw occurs when streams are reset during a pending write, corrupting memory and potentially leading to undefined behavior.

CVE-2026-123875: A medium-severity vulnerability causes the server to crash when a file download is canceled. This NULL dereference in the respondWithFile method can be triggered by a small number of canceled requests, resulting in a denial of service.

CVE-2026-123866: A high-severity use-after-free flaw in HTTP/2 stream teardown sends freed response memory to a peer. This can expose other users' response data, leading to information disclosure across different client sessions.

CVE-2026-123865: A high-severity memory and file descriptor leak occurs when HTTP/2 sessions fail during shutdown. The sessions are never cleaned up after a protocol error, causing resources to be permanently leaked and potentially exhausting system limits.

CVE-2026-48937: This vulnerability is noted as a prior gap that the fix for CVE-2026-123865 repairs, indicating a previous issue with session cleanup during shutdown that was not fully addressed.

CVE-2026-123868: A medium-severity flaw allows a client to send tiny one-byte frames that cause the server to retain disproportionate memory. This bypasses the maximum session memory limit, allowing a single stream to hold hundreds of megabytes and exhaust server resources.

CVE-2026-123828: A medium-severity one-byte heap overflow occurs in the session.altsvc method when an application passes a long authority value. This overflow aborts the process, leading to a crash and denial of service.

CVE-2026-126051: A high-severity vulnerability allows a remote client to crash TLS servers that use specific hooks. Deferred TLS handshake callbacks cause an uncaught exception that terminates the server process.

CVE-2026-123872: A high-severity TLS 1.2 renegotiation flaw allows a client to change the server name during the handshake. This bypasses client certificate checks, enabling a user with a normal login to access a host requiring stricter credentials.

CVE-2026-123867: A medium-severity mutual TLS bypass occurs when a host configured with only a CA falls back to the default CA. This allows the wrong client to gain access by exploiting the per-host configuration override.

CVE-2026-123871: A medium-severity information disclosure flaw exposes proxy credentials in error messages. The ERR_PROXY_INVALID_CONFIG error prints sensitive secrets into logs and crash reports, compromising credential security.

CVE-2026-123877: A medium-severity certificate validation bypass affects the https.Agent component. A cached TLS session from a broad trust policy is reused for a request with a stricter policy, incorrectly reporting the connection as authorized.

CVE-2026-123829: A low-severity vulnerability in the Permission Model leaks file names on macOS and Windows. Recursive file watching exposes the names of files that the model is supposed to deny access to.

CVE-2026-123862: A low-severity flaw causes an uncatchable assertion error when a pending zlib params call is followed by a destroy call. This rare usage pattern ends the process, leading to a crash.

CVE-2026-106071: A low-severity Permission Model flaw allows a wildcard lookup to over-grant file system access. The wildcard matches more paths than intended, bypassing the intended access restrictions.

CVE-2026-48615: This vulnerability is referenced as a prior issue that shares the lesson of exposing secrets in error messages, similar to the flaw addressed in CVE-2026-123871.

These vulnerabilities collectively present a critical risk to any organization running public-facing Node.js servers, particularly those utilizing HTTP/2 and HTTPS. The potential for remote denial of service and the exposure of sensitive cryptographic material and credentials demand immediate attention. Administrators should prioritize updating their runtime environments to mitigate these severe security gaps.

RECOMMENDATION:

We recommend you to update Node.js to version 22.23.5, 24.22.3, or 26.13.1 depending on your installed branch.

REFERENCES:

The following reports contain further technical details:

[/emaillocker]
crossmenu