Node.js Patches 16 Vulnerabilities, Two Allow HTTP/2 Server Crashes and Cross-Connection Data Leaks
Node.js maintainers released patches this week addressing 16 security vulnerabilities in the popular JavaScript runtime. Among the most serious are two flaws affecting Node's built-in HTTP/2 implementation. The first allows an unauthenticated client to crash servers running the 24.x and 26.x release lines simply by sending malformed or malicious requests, resulting in a denial-of-service condition. The second HTTP/2 issue can cause a server to send response data intended for one client connection to a different connection, raising the possibility of cross-connection data leakage.
HTTP/2 introduces multiplexing, allowing many requests and responses to share a single underlying connection. This efficiency gain comes with added implementation complexity, and bugs in stream handling, buffer management, or connection state tracking have historically led to both crash conditions and, in worse cases, data confusion between unrelated clients sharing infrastructure. Because Node.js underpins a vast number of backend services, APIs, and web applications, flaws in its core networking stack have broad reach — a single unpatched runtime can affect every application built on top of it, and unauthenticated DoS bugs are particularly attractive to attackers since no credentials or prior access are required to trigger them.
The practical risk depends on exposure: internet-facing services using Node's native HTTP/2 server support on the affected 24.x and 26.x branches are the most immediate concern, with availability and potential confidentiality impacts depending on deployment architecture. Organizations running multi-tenant or shared-connection environments should treat the data-leak variant with particular caution.
Defenders should prioritize identifying all Node.js instances in their environment, confirm which release lines and HTTP/2 configurations are in use, and apply the latest patched versions promptly. Where immediate patching isn't feasible, consider disabling HTTP/2 support or placing a hardened reverse proxy in front of affected services to filter malformed requests. Maintaining an accurate inventory of runtime versions across development and production environments remains essential for responding quickly to runtime-level vulnerabilities like these.
Source: The Hacker News
Read the original report ↗This is an original summary written by CyberSkii for reference. All rights to the underlying reporting remain with the publisher linked above.