nodejs · Node.js · published 2026-11-11
CVE-2026-123863Node.js is vulnerable to a remote HTTP/2 denial of service via a reachable assertion in Http2Session teardown
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-123863 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 44% of all CVEs. This Node.js vulnerability: CVSS 8.2 (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% (45th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.2 (v3.0)CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 reachable assertion in Node.js HTTP/2 session teardown lets any unauthenticated client abort the server, over both TLS and cleartext. A client can arrange for an Http2Stream that still holds nghttp2-allocated header buffers to outlive its session: the stream is removed from the session's stream set but never detached, so when ~Http2Session() runs the memory accounting is nonzero and the CHECK_EQ(current_nghttp2_memory_, 0) assertion fails, terminating the process. The trigger needs only a default http2 server whose handler responds before the request body has ended, which is typical. It is a variant of CVE-2024-27983 that the earlier fix did not cover, because that fix only detached streams still tracked in the session. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0).
Quoted from the CVE Program record.