Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Remote DoS in Node.js HTTP/2 via malformed HEADERS frame

IdentifiersCVE-2025-59465CWE-248

CVE-2025-59465 is a high-severity denial-of-service vulnerability in Node.js HTTP/2 server handling. A remote attacker can send a malformed HTTP/2 HEADERS frame containing oversized, invalid HPACK data, which causes Node.js to hit an unhandled TLSSocket error with code ECONNRESET. Instead of safely terminating only the offending connection, the process can crash. The issue is specifically described as affecting HTTP/2 over TLS and is primarily exposed in applications that do not register explicit error handlers on secure sockets, such as sockets surfaced through the server's secureConnection event. Reported affected release lines are Node.js 20.x, 22.x, 24.x, and 25.x.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote, unauthenticated attacker to crash a vulnerable Node.js process serving HTTP/2 over TLS, resulting in denial of service. The attacker does not need code execution; the outcome is service interruption through process termination. In production environments, this can take down externally exposed HTTP/2 services until the process is restarted or supervised recovery occurs.

Mitigation

If you can’t patch tonight, do this now.

As a workaround, attach explicit error handlers to secure TLS sockets so TLSSocket errors do not remain unhandled and crash the process. The content specifically gives the secureConnection event pattern as an example mitigation. More broadly, reduce exposure by disabling unnecessary HTTP/2/TLS listeners where feasible and ensuring process supervision/restart controls are in place, but the primary mitigation provided is explicit socket error handling.

Remediation

Patch, then assume compromise.

Upgrade Node.js to a fixed release in the supported lines. The provided content states that security releases addressing this issue were issued for Node.js 20.x, 22.x, 24.x, and 25.x, with released versions including 20.20.0, 22.22.0, 24.13.0, and 25.3.0. Apply the vendor security update appropriate to the deployed release line.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NodejsNodejsapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity17

Community discussion across Reddit, Mastodon, and other social sources.