CVSS 3.0
7.5 highCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVE-2026-123874 Node.js is vulnerable to an HTTP/2 use-after-free via respondWithFile() stream reset during a pending write
High (7.5) in nodejs node. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
On this page
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).
Severity
- EPSS
- 0.5% estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-416 Use After Free
- Published
- Modified
- Assigned by
- openjs (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123874 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123874?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123874?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123874 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-123874)
HTML:
<a href="https://cve.bz/cve/CVE-2026-123874"><img src="https://cve.bz/cve/badge/CVE-2026-123874.svg" alt="CVE-2026-123874"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| nodejs node | from 24.0.0 before 24.22.3 |
| nodejs node | from 25.0.0 before 26.13.1 |
Fix and patched versions
- Red Hat, Alpine, Alpaquita, BellSoft Hardened Containers: fixed package versions per release
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | nodejs | no fix listed | DEBIAN-CVE-2026-123874 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 and 5 more | nodejs | no fix listed | UBUNTU-CVE-2026-123874 |
| Red Hat | hummingbird:1 | nodejs22, nodejs22-bin, nodejs22-docs and 4 more | 1:22.23.4-2.3.2.3.1.hum1 | RHSA-2026:93603 |
| Red Hat | hummingbird:1 | nodejs22-npm | 1:10.9.9-1.22.23.4.2.3.2.3.1.hum1 | RHSA-2026:93603 |
| Red Hat | hummingbird:1 | nodejs24, nodejs24-bin, nodejs24-docs and 3 more | 1:24.22.3-0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs24-npm | 2:11.19.1-1.24.22.3.0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs24-npm-bin | 2:24.22.3-0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs26, nodejs26-bin, nodejs26-docs and 4 more | 1:26.13.1-0.1.hum1 | RHSA-2026:99436 |
| Red Hat | hummingbird:1 | nodejs26-npm | 1:11.20.0-1.26.13.1.0.1.hum1 | RHSA-2026:99436 |
| Red Hat | hummingbird:1 | v8-12.4-devel | 3:12.4.254.21-1.22.23.4.2.3.2.3.1.hum1 | RHSA-2026:93603 |
| Alpine | v3.21, v3.22 | nodejs | 22.23.5-r0 | ALPINE-CVE-2026-123874 |
| Alpine | v3.23, v3.24 | nodejs | 24.22.3-r0 | ALPINE-CVE-2026-123874 |
| Alpine | v3.24 | nodejs-current | 26.13.1-r0 | ALPINE-CVE-2026-123874 |
| Alpaquita | stream | nodejs22 | 22.23.5-r0 | BELL-CVE-2026-123874 |
| Alpaquita | stream | nodejs24 | 24.22.3-r0 | BELL-CVE-2026-123874 |
| Alpaquita | stream | nodejs26 | 26.13.1-r0 | BELL-CVE-2026-123874 |
| BellSoft Hardened Containers | stream | nodejs22 | 22.23.5-r0 | BELL-CVE-2026-123874 |
| BellSoft Hardened Containers | stream | nodejs24 | 24.22.3-r0 | BELL-CVE-2026-123874 |
| BellSoft Hardened Containers | stream | nodejs26 | 26.13.1-r0 | BELL-CVE-2026-123874 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine · Alpaquita · BellSoft Hardened Containers.
Red Hat
Red Hat rates this Important.
This vulnerability is rated as having Important impact because an unauthenticated remote attacker can cause memory corruption to terminate network processes, resulting in a denial of service without requiring privileges or user interaction. In typical Red Hat environments hosting Node.js services, the issue specifically impacts deployments using the core HTTP/2 implementation to transmit files directly via file-descriptor-backed streaming methods. Applications that do not enable HTTP/2 servers or handle static file delivery through alternative mechanisms are not exposed to this vulnerability.
Avoid stream.respondWithFile()/respondWithFD() for untrusted HTTP/2 clients; serve files over HTTP/1.1 or via a reverse proxy. Restrict HTTP/2 file-serving endpoints to trusted networks (see CME-202).
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | nodejs22-main-10.9.9-1.22.23.4.2.3.2.3.1.hum1 | Fixed 2026-11-02 | RHSA-2026:93603 |
| Red Hat Hardened Images | nodejs22-main-22.23.4-2.3.2.3.1.hum1 | Fixed 2026-11-02 | RHSA-2026:93603 |
| Red Hat Enterprise Linux 10 | nodejs22 | Not affected | |
| Red Hat Enterprise Linux 10 | nodejs24 | Affected | |
| Red Hat Enterprise Linux 10 | nodejs26 | Affected | |
| Red Hat Enterprise Linux 8 | nodejs:22/nodejs | Not affected | |
| Red Hat Enterprise Linux 8 | nodejs:24/nodejs | Affected | |
| Red Hat Enterprise Linux 9 | nodejs:22/nodejs | Not affected | |
| Red Hat Enterprise Linux 9 | nodejs:24/nodejs | Affected | |
| Red Hat Enterprise Linux 9 | nodejs:26/nodejs | Affected | |
| Red Hat Hardened Images | hi/nodejs | Under investigation | |
| Red Hat Hardened Images | nodejs20 | Will not fix | |
| Red Hat Hardened Images | nodejs24 | Affected | |
| Red Hat Hardened Images | nodejs25 | Will not fix | |
| Red Hat Hardened Images | nodejs26 | Affected | |
| Red Hat Hardened Images | npm12 | Under investigation |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-123874.