Node.js fixes 16 flaws, including HTTP/2 crashes and memory leaks
Node.js fixed 16 flaws, including HTTP/2 and TLS server bugs; update to 22.23.5, 24.22.3 or 26.13.1 if your process accepts those connections.
- Published
- Updated
- CVE
- CVE-2026-123863
CVE-2026-123866
CVE-2026-123864
CVE-2026-123865
CVE-2026-123874
CVE-2026-123875
CVE-2026-126051
CVE-2026-123872
CVE-2024-27983 - Ecosystem
- Node.jsWebsites and CMS
- Fixed in
- Node.js 22.23.5, 24.22.3, 26.13.1
- Exploitation
- No, The Hacker News says the Node.js advisory does not report any attacks using the flaws
Live scores
CVE-2026-123863- EPSS
- 0.005
low predicted chance of attack - VEDAS
- 0.514
likely exploited - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-123866- EPSS
- 0.005
low predicted chance of attack - VEDAS
- 0.051
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-123864- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.051
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-123865- EPSS
- 0.005
low predicted chance of attack - VEDAS
- 0.221
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-123874- EPSS
- 0.005
low predicted chance of attack - VEDAS
- 0.055
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-123875- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.052
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-126051- EPSS
- 0.008
low predicted chance of attack - VEDAS
- 0.052
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-123872- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.051
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2024-27983- EPSS
- 0.838
very likely to be attacked soon - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
What happened
The Node.js project released fixes for all three supported lines: 22.23.5, 24.22.3 and 26.13.1. The Hacker News reports that the release fixes 16 vulnerabilities in Node.js itself, seven of them rated high. HKCERT also published a bulletin on 12 Nov 2026 and rates the overall risk as Medium. It lists impacts of denial of service, security restriction bypass, sensitive information disclosure and data manipulation. HKCERT CCCS Canada also published an advisory, AV26-1156. CCCS Canada We only had its headline, so we do not repeat its contents here.
Details below are from The Hacker News, which summarises the Node.js advisory:
- CVE-2026-123863 (high): unauthenticated clients can crash servers using built-in HTTP/2 on the 24.x and 26.x lines. It needs a default HTTP/2 server that replies before the request body has fully arrived. It works over both TLS and cleartext.
- CVE-2026-123866 (high): an HTTP/2 flaw that can make a server send a client pieces of its memory, including responses meant for other connections. It affects all three lines. From 24.22.0 and 26.9.0 onward a client alone can trigger it. On 22.x and older 24.x and 26.x builds it needs the server itself to close a stream partway through a response.
- CVE-2026-123864 (high): in HTTPS servers, an unauthenticated client may read memory from other connections, “including TLS private keys and other users’ requests,” per the project. It needs a handler that calls res.flushHeaders() before the request body has fully arrived and later calls res.end() with data. Reading the leaked memory also needs a route that sends back or stores a request body. Plain node:http servers are not affected.
- CVE-2026-123865 (high): a client can make any default HTTP/2 server hold memory and file descriptors permanently, on all three lines.
- CVE-2026-123874 (high): a client can corrupt server memory on 24.x and 26.x when files are served with stream.respondWithFile() or stream.respondWithFD(). Canceling such downloads can also crash the server on all three lines (CVE-2026-123875, medium).
- CVE-2026-126051 (high): a client can crash a TLS server on 24.x and 26.x if it uses the SNICallback, OCSPRequest, newSession or resumeSession hooks, or server.addContext().
- CVE-2026-123872 (high): on a TLS server with stricter client-certificate rules for some hostnames, a client approved for another hostname can switch to a stricter one during TLS 1.2 renegotiation without meeting its rules. All three lines are affected.
The Hacker News says five of the flaws, including CVE-2026-123863 and CVE-2026-123864, were reported by Chris Rohlf in collaboration with Claude and Anthropic Research, according to the advisory.
The outlets differ on counts. HKCERT’s identifier list has 19 entries, including CVE-2024-27983, while The Hacker News counts 16 vulnerabilities fixed in Node.js itself. We do not have enough detail to reconcile the two.
Am I affected?
HKCERT lists Node.js versions prior to 22.23.5, 24.22.3 and 26.13.1 as affected. HKCERT
According to The Hacker News, the eight flaws detailed above are all in Node.js’s own HTTP/2, HTTPS and TLS server code, so they matter where a Node.js process accepts those connections itself. Several also depend on specific handler behavior or on the 24.x and 26.x lines, as listed above. End-of-life lines, including 20.x and 25.x, get no fix in this release, and the project says such versions are always affected. The Hacker News
What to do now
- Update to the fixed version for your line: 22.23.5, 24.22.3 or 26.13.1. HKCERT advises checking the vendor site for details before installing. HKCERT
- Identify which services terminate HTTP/2, HTTPS or TLS directly in Node.js, and update those first.
- If you run an end-of-life line such as 20.x or 25.x, move to a supported line. No fix is provided for those versions. The Hacker News
- Do not plan around a workaround. The project’s advisory lists none for servers that cannot update yet, according to The Hacker News.
- Whether servers that met the conditions for CVE-2026-123864 should replace TLS keys or other secrets after updating is not confirmed. The Hacker News notes the advisory does not say. Treat that as your own risk decision.
Update, 15 November 2026
- The Hacker News says the Node.js security advisory does not report any attacks using these flaws. (thehackernews.com)
- The Hacker News says CVE-2026-123864, the HTTPS memory-leak flaw, affects all three supported lines (22.x, 24.x and 26.x). (thehackernews.com)
- HKCERT’s bulletin links the Node.js project’s own advisory at nodejs.org/en/blog/vulnerability/november-2026-security-releases, plus release notes for v22.23.5, v24.22.3 and v26.13.1, as the vendor source. (hkcert.org)