nodejs · Node.js · published 2026-11-11
CVE-2026-123868Node.js is vulnerable to an HTTP/2 memory exhaustion denial of service via unaccounted inbound DATA on an undrained stream
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-123868 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 42% of all CVEs. This Node.js vulnerability: CVSS 5.9 (v3.0). 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% (42th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.9 (v3.0)CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | 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)#
An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that queue to current_session_memory_: the socket read buffer is accounted only during parsing and released immediately, so whatever stays queued is accounted to nothing. A peer that fills a stream's receive window with one-byte DATA frames pays about 10 wire bytes per frame while the server retains about 114 bytes per frame, so a single stream on one connection can retain hundreds of megabytes from tens of megabytes sent. maxSessionMemory neither bounds the growth nor refuses new streams, because Http2Session::CanAddStream gates admission on the same counter that never sees the queue. This vulnerability affects Node.js 26.x and 24.x.
Quoted from the CVE Program record.