dbcve.org
Node.jsApplication

CVE-2025-59465

HIGH · 7.5 CVSS v3.1 Published 2026-01-20
Fix available
A fix is available. Upgrade to 20.20.0 / 22.22.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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) }) }) ```

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Node.js HTTP/2 implementation fails to handle malformed HEADERS frames with oversized, invalid HPACK data, triggering an unhandled TLSSocket ECONNRESET error that crashes the process. This is a denial-of-service vulnerability affecting Node.js servers using HTTP/2 over TLS without proper error handlers on secure sockets.

MitigationUpgrade Node.js to the patched version or ensure all secure connections have explicit error handlers attached to prevent unhandled TLSSocket errors from crashing the process.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Node.jsApplication
Affected:>= 20.0.0, < 20.20.0>= 22.0.0, < 22.22.0>= 24.0.0, < 24.13.0>= 25.0.0, < 25.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Node.js version
    Run 'node --version' to get the installed Node.js version
    Affected if Version falls within >= 20.0.0 and < 20.20.0, OR >= 22.0.0 and < 22.22.0, OR >= 24.0.0 and < 24.13.0, OR >= 25.0.0 and < 25.3.0
  2. Identify HTTP/2 usage
    Search codebase for require('http2') or usage of http2.createSecureServer, or check if the application serves HTTP/2 over TLS
    Affected if Application uses http2.createSecureServer or http2 over TLS connections
  3. Check for secure socket error handlers
    Search for .on('error', ...) or .addListener('error', ...) calls on TLSSocket or secure connection objects, particularly within 'secureConnection' event handlers
    Affected if No explicit error event handler is attached to secure sockets handling HTTP/2 traffic
  4. Verify TLS is in use
    Confirm the HTTP/2 server is configured with TLS/HTTPS (check server options for key/cert or https module usage)
    Affected if HTTP/2 runs over TLS (h2 or h2c protocol)

If the Node.js version is in the affected range, HTTP/2 over TLS is in use, and no error handlers are attached to secure sockets, the application is vulnerable to process crashes from malformed HEADERS frames.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 20.20.0 / 22.22.0 / 24.13.0 or later
Fixed in 20.20.022.22.024.13.0
Interim mitigation

Upgrade Node.js to the patched version or ensure all secure connections have explicit error handlers attached to prevent unhandled TLSSocket errors from crashing the process.

Recommended fix High confidence

Node.js 20.20.0, 22.22.0, 24.13.0, or 25.3.0 (depending on your major version line)

  1. Identify your current Node.js version by running 'node --version'
  2. Determine which major version line you are using (20.x, 22.x, 24.x, or 25.x)
  3. For Node.js 20.x users: Upgrade to version 20.20.0 or later
  4. For Node.js 22.x users: Upgrade to version 22.22.0 or later
  5. For Node.js 24.x users: Upgrade to version 24.13.0 or later
  6. For Node.js 25.x users: Upgrade to version 25.3.0 or later
  7. Use a version manager like nvm to switch versions: 'nvm install <fixed_version>' and 'nvm use <fixed_version>','Verify the upgrade was successful by running 'node --version'
  8. Test your application to ensure it functions correctly with the new version
Caveat Minor/patch releases typically have minimal breaking changes, but review the release notes for your target version to confirm compatibility with your application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Node.js Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59465 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59465 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data