CVE-2026-123874: Node.js is vulnerable to an HTTP/2 use-after-free via respondWithFile() stream reset during a pending write

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 10 Nov 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

0.5%

EPSS score, percentile 41.1 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?

7.5 High

CVSS v3.0 base score, given by the CNA

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

Advisories and patches (1)

Which versions are affected?

Affected

• from 24.0.0 to before 24.22.3
• from 25.0.0 to before 26.13.1

Versions by product

Source: CISA KEV 2026.11.10, as of 10 Nov 2026; FIRST EPSS, as of 12 Nov 2026; CVE List, as of 12 Nov 2026. About the data.

Description

Node.js is vulnerable to an HTTP/2 use-after-free via respondWithFile() stream reset during a pending write

A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext, when the server serves files with respondWithFile() or respondWithFD(). A client can make the server free an Http2Stream while a write request that points to it is still queued on the socket; when that write completes, the code dereferences and makes a virtual call through the freed object. The only precondition is that the application serves a file with stream.respondWithFile() or stream.respondWithFD(), with default settings otherwise. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0).

Source: CVE List, as of 12 Nov 2026. About the data.

What to do

Advisories and patches

• nodejs.org (Vendor advisory)

This summary is based on the CVE record as of 12 Nov 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

Source: CVE List, as of 12 Nov 2026. About the data.

Timeline