nodejs · Node.js · published 2026-11-11
CVE-2026-123874Node.js is vulnerable to an HTTP/2 use-after-free via respondWithFile() stream reset during a pending write
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-123874 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 46% of all CVEs. This Node.js vulnerability: CVSS 7.5 (v3.0), attacks can be automated. Fixed upstream in Node.js 26.13.1, 24.22.3, 22.23.5; Debian and Ubuntu still have unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Node.js 26.13.1, 24.22.3, 22.23.5.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | nodejs | No fix yet |
| 12 bookworm | nodejs | No fix yet | |
| Ubuntu | 26.04 LTS | nodejs | No fix yet |
| 24.04 LTS | nodejs | No fix yet | |
| Red Hat Enterprise Linux (+3 more packages) | RHEL 9 | nodejs | Not affected |
| RHEL 8 | nodejs | Not affected |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Language runtimeNode.js
Node.js security releases: 26.13.1, 24.22.3, 22.23.5
Upgrade to
26.13.124.22.322.23.5Why: Vendor security release for server software (most severe: CVE-2026-123863).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.5% (47th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.0)CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- nodejs node
24.0.0to before24.22.3(affected)25.0.0to before26.13.1(affected)
Description (from the CVE record)#
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).
Quoted from the CVE Program record.