Vulnerability · CVE-2026-123874
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 respond
Published Nov 11, 2026 · catalog updated Nov 12, 2026 · Red Hat Red Hat Enterprise Linux
Last checked Nov 12, 2026. A connected source was read within the last 7 days.
Open the advisory
Exploitation likelihood is not on this record for CVE-2026-123874. A missing EPSS score is not a low risk. Compare Red Hat Red Hat Enterprise Linux with the linked advisory before you change production.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
Same product and reporting
- CVE-2026-126051 · High
- CVE-2026-123875 · Medium
- CVE-2026-123872 · High
- CVE-2026-123877 · Medium
- CVE-2026-123871 · Medium
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Not in the current FIRST EPSS dataset
- Remediation
- Advisory link
- Affected products
- Alpine:v3.21 nodejs · Alpine:v3.22 nodejs · Alpine:v3.23 nodejs · Alpine:v3.24 nodejs · Debian:12 nodejs · Debian:13 nodejs
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).
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Alpine:v3.21 nodejs0 → 22.23.5-r0
- Alpine:v3.22 nodejs0 → 22.23.5-r0
- Alpine:v3.23 nodejs0 → 24.22.3-r0
- Alpine:v3.24 nodejs0 → 24.22.3-r0
- Debian:12 nodejs18.13.0+dfsg1-1, 18.13.0+dfsg1-1.1, 18.19.0+dfsg-1
- Debian:13 nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2
- Debian:14 nodejs20.19.2+dfsg-1, 20.19.4+dfsg-1, 20.19.5+dfsg+~cs20.19.12-1
How to fix CVE-2026-123874
Upgrade
CVE-2026-123874 lists a fix boundary at 22.23.5-r0. Compare the installed build with that boundary before you change production.
Version check
Fixed in 22.23.5-r0 · 9 other ranges on the advisory
Advisory
Open the redhat record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for CVE-2026-123874. A missing EPSS score is not a low risk. Compare Red Hat Red Hat Enterprise Linux with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with 0 → 22.23.5-r0, 0 → 24.22.3-r0, 18.13.0+dfsg1-1, 18.13.0+dfsg1-1.1, 18.19.0+dfsg-1, 20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2, 20.19.2+dfsg-1, 20.19.4+dfsg-1, 20.19.5+dfsg+~cs20.19.12-1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-825. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Nov 11, 2026 · OpenSSF OSV / OSV Scanner
Detected
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 free
Nov 12, 2026 · OpenSSF OSV / OSV Scanner
Updated
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 free
Nov 12, 2026 · Trivy Vulnerability DB
Fix available
nodejs fixed in 22.23.5-r0; nodejs fixed in 22.23.5-r0; nodejs fixed in 24.22.3-r0; nodejs fixed in 24.22.3-r0
Nov 12, 2026 · Trivy Vulnerability DB
Fix available
nodejs fixed in 22.23.5-r0
Nov 12, 2026 · Trivy Vulnerability DB
Fix available
nodejs fixed in 24.22.3-r0
Nov 12, 2026 · Trivy Vulnerability DB
Updated
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 free
Sources
- OpenSSF OSV / OSV ScannerPackage advisoryDEBIAN-CVE-2026-123874osv.dev
- Red Hat Security DataVendor advisoryCVE-2026-123874
nodejs: nodejs: Denial of Service via HTTP/2 use-after-free
access.redhat.com - Trivy Vulnerability DBPackage advisoryALPINE-CVE-2026-123874
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 i
osv.dev
References
Freshness
Last verified in this catalog Nov 12, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- Trivy Vulnerability DBNov 12, 2026
- Red Hat Security DataNov 12, 2026
- OpenSSF OSV / OSV ScannerNov 12, 2026