$ techbeacon▋
CVE & Exploits

Critical Node.js HTTP/2 Vulnerabilities Patched After Server Crash and Data Leak Risks

Critical Node.js HTTP/2 Vulnerabilities Patched After Server Crash and Data Leak Risks

Node.js developers released emergency updates this week that close two serious flaws in the runtime's native HTTP/2 implementation, flaws that could let unauthenticated clients bring down servers or siphon memory belonging to other connections.

The first vulnerability, present in the 24.x and 26.x release branches, allowed a malicious client to send specially crafted HTTP/2 frames that triggered a denial‑of‑service condition, crashing the server process without any authentication check. A second issue, discovered shortly thereafter, could cause the server to inadvertently expose fragments of its own memory—including responses meant for other users—when handling certain HTTP/2 streams.

Both problems were initially reported by security researchers and highlighted on The Hacker News, prompting the Node.js core team to prioritize patches. The fixes were merged into the latest point releases and are now available for download from the official distribution channels. The team also issued advisory notes urging operators to upgrade immediately, especially those running production services that rely on the built‑in HTTP/2 module.

Node.js powers a large share of modern web back‑ends, from small startups to enterprise‑grade platforms, and its built‑in HTTP/2 support is frequently enabled to take advantage of multiplexed streams and reduced latency. Because the vulnerabilities required no credentials, any external entity that could reach a vulnerable server could potentially exploit the bugs, making the risk surface broad. Organizations that have not yet applied the updates may still be exposed, and security auditors recommend verifying the patch level on all deployed instances.

Beyond the immediate patches, the incidents underscore a recurring theme in web‑protocol security: newer features like HTTP/2, while offering performance gains, also expand the attack surface. Developers are advised to consider additional mitigations such as disabling HTTP/2 until the runtime is confirmed secure, employing network‑level rate limiting, and monitoring for anomalous frame patterns that could indicate an exploit attempt.

Looking ahead, the Node.js community says the incident will drive a more thorough review of the HTTP/2 code path and may inspire stricter testing regimes for future releases. For now, the priority remains clear: administrators should pull the latest 24.x or 26.x updates, confirm that the built‑in HTTP/2 module is patched, and review their security policies to ensure that similar vulnerabilities are caught before they can be weaponized.

Deepak Chandra Meena — Deepak covers the dark web and underground hacking forums, reporting on marketplace activity and access broker listings. Monitors Tor-based forums and encrypted leak channels.

Comments (0)

Be the first to comment.

Join the discussion

Protected by reCAPTCHA v3

Related