CVE.org (no NVD analysis yet)· CNA openjs

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

HighCVSS 7.5 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: nodejs node 24.22.3, 26.13.1.

Low priority for now. Upgrade to nodejs node 24.22.3, 26.13.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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).

EUVD-2026-123701

Published: Nov 11, 2026
Updated: Nov 12, 2026
EPSS: 0.4% · 41th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CNA vs NVD score

NVD: —
CNA · openjs: 7.5; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Using node? Add it to your stack and be the first to know about CVEs like this one. (Node.js)

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openjs). Independent of NVD's CPE analysis and usually ahead of it.

nodejs node
- 24.0.0 and later · before 24.22.3affected · semver
- 25.0.0 and later · before 26.13.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.21	nodejs	before 22.23.5-r0	22.23.5-r0
Alpine:v3.23	nodejs	before 24.22.3-r0	24.22.3-r0
Alpine:v3.24	nodejs-current	before 26.13.1-r0	26.13.1-r0
Debian:12	nodejs	from 0	—

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

CVE-2024-27983An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2…
57Plan
CVE-2025-27210An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.
34Monitor
CVE-2026-123872Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change
32Monitor

Published before and after this one in the same product

← EarlierCVE-2026-123868Nov 11, 2026 · Node.js is vulnerable to an HTTP/2 memory exhaustion denial of service via unaccounted inbound DATA on an undrained stream
23Monitor
← EarlierCVE-2026-123871Nov 11, 2026 · Node.js is vulnerable to proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages
24Monitor
Later →CVE-2026-123875Nov 11, 2026 · Node.js is vulnerable to an HTTP/2 denial of service via a NULL pointer dereference when a respondWithFile() download is cancelled
23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
nodejs node	24.22.3	Vendor (CNA)
nodejs node	26.13.1	Vendor (CNA)
alpine:nodejs	22.23.5-r0 · Alpine:v3.21	Package registry (OSV)
alpine:nodejs-current	26.13.1-r0 · Alpine:v3.24	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedNov 11, 2026
Fix recordedNov 11, 2026same day
TodayNov 13, 2026+2 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Chris Rohlf in collaborationClaude and Anthropic Researchreporter
mcollinaremediation developer
UlisesGasconremediation reviewer
aduh95coordinator

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-1238640 days apartNode.js is vulnerable to cross-connection memory disclosure via TLS write re-entrancy in the HTTPS request parser
32Monitor
CVE-2026-1238660 days apartNode.js is vulnerable to HTTP/2 response memory disclosure via a use-after-free during stream teardown
30Monitor
CVE-2026-5684899 days apartA flaw in Node.js HTTP/2 handling allows `nghttp2_session_mem_send()` to be called re-entrantly while `nghttp2_session_mem_recv()` is…
30Monitor

Bug bounty scope

Node.jsHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: patch commit or PR link.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (2)

Exploit maturity— → noneNov 11, 2026, 8:07 PM UTC
Fix✗ → ✓Nov 11, 2026, 8:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

cna.openjsf.org/security-advisories.html

Show all references (1 more)

nodejs.org/en/blog/vulnerability/november-2026-security-releases

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records