CVE-2025-59465 Vulnerability Analysis & Exploit Details

CVE-2025-59465
Vulnerability Scoring

7.5

/10

Very High Risk

Highly exploitable, CVE-2025-59465 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

Attack Complexity: Low
Exploits can be performed without significant complexity or special conditions.
Attack Vector: Network
Vulnerability is exploitable over a network without physical access.
Privileges Required: None
No privileges are required for exploitation.
Scope: Unchanged
Exploit remains within the originally vulnerable component.
User Interaction: None
No user interaction is necessary for exploitation.

CVE-2025-59465 Details

Status: Analyzed

Last updated: 🕗 30 Jan 2026, 20:25 UTC
Originally published on: 🕘 20 Jan 2026, 21:16 UTC

Time between publication and last update: 9 days

CVSS Release: version 3

CVSS3 Source

support@hackerone.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE-2025-59465 Vulnerability Summary

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`. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example: ``` server.on('secureConnection', socket => { socket.on('error', err => { console.log(err) }) }) ```

Assessing the Risk of CVE-2025-59465

Access Complexity Graph

The exploitability of CVE-2025-59465 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-59465

With low attack complexity and no required privileges, CVE-2025-59465 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-59465, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-59465, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: None
CVE-2025-59465 has no significant impact on data confidentiality.
Integrity: None
CVE-2025-59465 poses no threat to data integrity.
Availability: High
CVE-2025-59465 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2025-59465 References

External References

https://nodejs.org/en/blog/vulnerability/december-2025-security-releases

CWE Common Weakness Enumeration

CWE-400

CAPEC Common Attack Pattern Enumeration and Classification

XML Ping of the Death CAPEC-147 An attacker initiates a resource depletion attack where a large number of small XML messages are delivered at a sufficiently rapid rate to cause a denial of service or crash of the target. Transactions such as repetitive SOAP transactions can deplete resources faster than a simple flooding attack because of the additional resources used by the SOAP protocol and the resources necessary to process SOAP messages. The transactions used are immaterial as long as they cause resource utilization on the target. In other words, this is a normal flooding attack augmented by using messages that will require extra processing on the target.
Sustained Client Engagement CAPEC-227 An adversary attempts to deny legitimate users access to a resource by continually engaging a specific resource in an attempt to keep the resource tied up as long as possible. The adversary's primary goal is not to crash or flood the target, which would alert defenders; rather it is to repeatedly perform actions or abuse algorithmic flaws such that a given resource is tied up and not available to a legitimate user. By carefully crafting a requests that keep the resource engaged through what is seemingly benign requests, legitimate users are limited or completely denied access to the resource.
Regular Expression Exponential Blowup CAPEC-492 An adversary may execute an attack on a program that uses a poor Regular Expression(Regex) implementation by choosing input that results in an extreme situation for the Regex. A typical extreme situation operates at exponential time compared to the input size. This is due to most implementations using a Nondeterministic Finite Automaton(NFA) state machine to be built by the Regex algorithm since NFA allows backtracking and thus more complex regular expressions.

Vulnerable Configurations

cpe:2.3:a:nodejs:node.js:20.0.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.0.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.1.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.1.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.2.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.2.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.3.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.3.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.3.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.3.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.4.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.4.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.5.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.5.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.5.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.5.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.6.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.6.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.6.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.6.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.7.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.7.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.8.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.8.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.8.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.8.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:20.9.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.9.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.10.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.10.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.11.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.11.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.11.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.11.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.12.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.12.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.12.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.12.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.12.2:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.12.2:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.13.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.13.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.13.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.13.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.14.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.14.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.15.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.15.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.15.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.15.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.16.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.16.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.17.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.17.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.18.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.18.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.18.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.18.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.18.2:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.18.2:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.18.3:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.18.3:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.19.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.19.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.19.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.19.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.19.2:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.19.2:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.19.3:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.19.3:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.19.4:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:20.19.4:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.0.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.0.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.1.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.1.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.2.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.2.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.3.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.3.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.4.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.4.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.4.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.4.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.5.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.5.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.5.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.5.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.6.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.6.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.7.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.7.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.8.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.8.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.9.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.9.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.10.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.10.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:22.11.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.11.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.12.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.12.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.13.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.13.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.13.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.13.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.14.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.14.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.15.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.15.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.15.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.15.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.16.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.16.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.17.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.17.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.17.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.17.1:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.18.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:22.18.0:*:*:*:lts:*:*:*
cpe:2.3:a:nodejs:node.js:24.0.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.0.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.0.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.0.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.0.2:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.0.2:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.1.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.1.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.2.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.2.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.3.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.3.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.4.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.4.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.4.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.4.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.5.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.5.0:*:*:*:-:*:*:*

Protect Your Infrastructure against CVE-2025-59465: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2026-23039 – In the Linux kernel, the following vulnerability has been resolved: drm/gud: fix NULL fb and crtc dereferences on USB disconnect On disconnect dr...
CVE-2026-23038 – In the Linux kernel, the following vulnerability has been resolved: pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() In nfs4_ff_a...
CVE-2026-23037 – In the Linux kernel, the following vulnerability has been resolved: can: etas_es58x: allow partial RX URB allocation to succeed When es58x_alloc_...
CVE-2026-23036 – In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before iget_failed() in btrfs_read_locked_inode() In btrf...
CVE-2026-23035 – In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv mlx5e_priv is ...