CVE-2025-59465

A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` error `ECONNRESET`

High · published January 20, 2026

CVSS v3.0
7.5
EPSS
4%
Percentile
90.4
In the wild
Unconfirmed
What it is

⚡ A malformed HTTP/2 frame can crash your Node.js app, triggering a remote denial of service! It's like someone throwing a wrench into a busy assembly line and stopping everything. 🛠️ Think of your Node.js server as a well-oiled restaurant kitchen. If a waiter delivers an oversized, bad order ticket that the kitchen can't handle, it could cause chaos, leading to a complete shutdown instead of just managing the error smoothly. This is exactly what's happening here! An attacker could exploit this flaw to send invalid HPACK data, causing the connection to crash instead of gracefully handling the error. This could lead to service downtime, frustrating users, and potentially resulting in lost revenue. An unhandled error means your application is wide open to disruptions!

Put simply

Think of your Node.js server as a well-oiled restaurant kitchen. If a waiter delivers an oversized, bad order ticket that the kitchen can't handle, it could cause chaos, leading to a complete shutdown instead of just managing the error smoothly. This is exactly what's happening here! This vulnerability arises when a malformed HTTP/2 HEADERS frame triggers an unhandled TLSSocket error (ECONNRESET), causing Node.js to crash. Applications that fail to attach explicit error handlers for secure sockets are particularly at risk.

What to do

An attacker could exploit this flaw to send invalid HPACK data, causing the connection to crash instead of gracefully handling the error. This could lead to service downtime, frustrating users, and potentially resulting in lost revenue. An unhandled error means your application is wide open to disruptions! To mitigate this, ensure your application includes explicit error handlers for secure sockets. For instance, implement something like 'socket.on('error', err => { console.log(err); })' in your secure connection events. Additionally, review your Node.js version for any available patches related to this vulnerability. You've got this! With a few tweaks, you can keep your Node.js application running smoothly and securely. 🛡️

The record
Technical detail
CVSS v3.0
7.5 · HIGH
Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS v4.0
Not supplied
EPSS
0.03962 · 90.4th percentile
Published
2026-01-20T20:41Z
EPSS history
Timeline
  • 20 JAN 20:41Z
    A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` error `ECONNRESET`
    cvelistv5