CVE-2026-123865: An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors
Source GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.5 High · fixed in 26.13.1 : patch node soon.
Data as of 11 Nov 2026, 22:34 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.0 | 7.5 |
|---|
- Patch
- Available – fixed in 26.13.1, 24.22.3, 22.23.5
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade node to 26.13.1, 24.22.3 or 22.23.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nodejsnode | Affected
| Fixed in
|
| nodejsnode | Affected
| Fixed in
|
| nodejsnode | Affected
| Fixed in
|
npmnodepkg:npm/nodeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, monitoring for unusual resource usage and limiting exposure of HTTP/2 services may help mitigate impact.
Description
An unauthenticated HTTP/2 client can cause a Node.js server to leak memory and file descriptors indefinitely by triggering a protocol error during session shutdown. This leaves sockets in CLOSE_WAIT state and HTTP/2 session state held in memory without release. The issue affects Node.js versions 22.x, 24.x, and 26.x and is a partial regression of a previous fix (CVE-2026-48937).