# CVE-2025-59465: Denial of service in node

> Remote attackers can crash Node.js servers by sending malformed HTTP/2 headers, causing denial of service in applications lacking explicit socket error handlers.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jan 2026
- **Updated:** 15 Jul 2026
- **Also known as:** ALPINE-CVE-2025-59465, AZL-75077, BELL-CVE-2025-59465, BIT-node-2025-59465, BIT-node-min-2025-59465, CLEANSTART-2026-UP28744, DEBIAN-CVE-2025-59465, GHSA-w2pg-hw7v-f7m9, MINI-68mv-3q5m-hq2m, MINI-8333-ggg3-6vwc, MINI-9v7j-p2w9-8fvj, MINI-m6vj-v627-r859, MINI-m84f-3g4p-2v3m, MINI-r4vm-xh72-wv8w, MINI-w3cf-mxh4-xrj3, UBUNTU-CVE-2025-59465

## What is CVE-2025-59465?

CVE-2025-59465 is a high-severity denial of service vulnerability in Nodejs Node.js, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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)
  })
})
```

Weakness: CWE-248 (Uncaught Exception), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-59465?

2 open source packages ship an affected version, including node and node-min. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 20.20.0, 22.22.0, 24.13.0, 25.3.0 |
| `node-min` | Bitnami | All versions | 20.20.0, 22.22.0, 24.13.0, 25.3.0 |

Products: Nodejs Node.js.

## How do I fix CVE-2025-59465?

Upgrade node to a fixed version for your release line: 20.20.0, 22.22.0, 24.13.0 or 25.3.0.

## Is CVE-2025-59465 being exploited?

There is no known exploitation of CVE-2025-59465 in the wild and no public exploit code.

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59465 and fix it if it is affected.

What it is: CVE-2025-59465 is a high-severity denial of service vulnerability in Nodejs Node.js, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59465 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 20.20.0, 22.22.0, 24.13.0, 25.3.0
- node-min (Bitnami): affected all versions; fixed in 20.20.0, 22.22.0, 24.13.0, 25.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59465/ (Markdown: https://insights.sbomify.com/CVE-2025-59465/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59465
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59465
- OSV: https://osv.dev/vulnerability/CVE-2025-59465

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59465/
Summaries are generated and may contain mistakes; the official description above is the record.