Node.js November 2026 security release fixes HTTP/2, HTTPS and TLS flaws
Identifiers: CVE-2026-123863 · CVE-2026-123864 · CVE-2026-123865 · CVE-2026-123866 · CVE-2026-126051 · CVE-2026-123872 · CVE-2026-123874 · CVE-2026-123828 · CVE-2026-123867 · CVE-2026-123868 · CVE-2026-123871 · CVE-2026-123877 · CVE-2026-123875 · CVE-2026-123829 · CVE-2026-123862 · CVE-2026-106071
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
On 11 November 2026 the Node.js project published a security release for the 22.x, 24.x and 26.x lines, with fixed versions 22.23.5, 24.22.3 and 26.13.1. The umbrella announcement describes sixteen issues, the highest rated High, concentrated in the HTTP/2 server, HTTPS request parsing, TLS handshake and client-certificate handling, the https.Agent session cache, proxy error messages, zlib streaming and the Permission Model. Each flaw has its own preconditions. This is not a single unauthenticated remote code execution that applies to every Node application.
Impact
Worst cases described upstream are server process crashes, memory and file-descriptor leaks, and memory exhaustion caused by HTTP/2 clients; disclosure of other connections' memory over HTTPS under a specific handler pattern; and client-certificate policy bypasses on servers that apply different rules per hostname. None of these describes exposure of a particular site until you know how that site uses Node and where TLS terminates.
Who is affected
Lines listed per issue in the umbrella: CVE-2026-123863, CVE-2026-126051, CVE-2026-123874, CVE-2026-123828 and CVE-2026-123868 list 24.x and 26.x; CVE-2026-123864, CVE-2026-123865, CVE-2026-123866, CVE-2026-123872, CVE-2026-123867, CVE-2026-123871, CVE-2026-123877, CVE-2026-123875, CVE-2026-123829, CVE-2026-123862 and CVE-2026-106071 list 22.x, 24.x and 26.x. The 22.23.5 release notes also carry fixes for some items the umbrella lists for 24.x and 26.x only; take the fix without treating that as proof 22.x was exposed. Conditions matter: CVE-2026-123864 needs Node's own HTTPS server with a handler that flushes headers before the request body ends and later ends the response with a non-empty chunk, and reading the leaked memory also needs an ordinary route that echoes or stores a request body; cleartext node:http is not affected. HTTP/2 issues need an actual node:http2 server, and several are reachable over cleartext; CVE-2026-123874 and CVE-2026-123875 also need respondWithFile or respondWithFD, and CVE-2026-123828 needs attacker-controlled input passed to altsvc. CVE-2026-126051 needs SNI, OCSP or session hooks or addContext. CVE-2026-123872 and CVE-2026-123867 need per-hostname client-certificate policies. CVE-2026-123877 affects outbound https.Agent use with mixed CA options. CVE-2026-123871 needs a malformed proxy URL in the environment. CVE-2026-123862 needs zlib params during streaming. The Permission Model items apply only under --permission, and CVE-2026-123829 only on macOS and Windows. The upstream announcement treats end-of-life lines as always affected; they receive no fix in this upstream release.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| Node.js 22.x | 22.x before 22.23.5; per-issue branch and feature conditions apply | 22.23.5 |
| Node.js 24.x | 24.x before 24.22.3; per-issue branch and feature conditions apply | 24.22.3 |
| Node.js 26.x | 26.x before 26.13.1; per-issue branch and feature conditions apply | 26.13.1 |
Exploitation evidence
Exploitation not established. No in-the-wild exploitation was established in the reviewed upstream sources, and none of these identifiers appeared in CISA KEV at review time. Absence is not proof that nobody has tried.
Actions
- Identify the Node major actually serving traffic (22, 24 or 26) and the exact version reported by the running process, not the version in a Dockerfile or on a developer machine.
- Move to 22.23.5, 24.22.3 or 26.13.1 by rebuilding the application image or updating the managed runtime, then redeploy and restart; keep the previous artifact for rollback.
- If the image is your own build, rebuild it from an updated base image. If it is a vendor-supplied image, move to the vendor's updated supported tag or follow the vendor's documented build procedure; do not replace the node binary inside the image, and do not rebuild it independently as a substitute for a supported release.
- Note where TLS terminates: a Node HTTPS server is in scope for CVE-2026-123864, while a cleartext node:http backend behind a TLS edge is not, though the edge's own TLS stack has its own update stream.
- Check whether any Node process runs an http2 server, uses respondWithFile, per-hostname TLS contexts, SNI or OCSP hooks, or the Permission Model, since those decide which issues could apply.
- Confirm completion from a running process or image digest, and watch memory use and restart counts after deployment.
- If on an end-of-life line such as 20 or earlier, plan a major upgrade; this upstream release carries no fix for those lines.
Unknowns
- Exact earlier versions where each flaw was introduced vary per issue and are not stated in the umbrella; 123866 notes its remote-only trigger depends on a window-size change present since 26.9.0 and 24.22.0.
- As of November 22, 2026, CVE-2026-123873 (heap snapshot destination) is absent from the nodejs.org Notable Changes pages for 22.23.5, 24.22.3 and 26.13.1 and from the November 11 umbrella notice, but it is listed in the Node.js project's GitHub release entries for those exact versions, while CVE-2026-106071 appears in the umbrella notice and not in those nodejs.org Notable Changes lists. This briefing keeps its stable record on the sixteen umbrella issues, treats the GitHub listings as corroborating release notes rather than adding CVE-2026-123873 to the main affected ranges, and leaves the three published update versions and patch guidance unchanged.
- Whether a specific site's handlers match the HTTPS or HTTP/2 preconditions; this needs a look at application code and proxy topology.
- Timing of managed-platform and container base-image updates.
Sources
- Node.js project https://nodejs.org/en/blog/vulnerability/november-2026-security-releases
- Node.js project https://nodejs.org/en/blog/release/v22.23.5
- Node.js project https://nodejs.org/en/blog/release/v24.22.3
- Node.js project https://nodejs.org/en/blog/release/v26.13.1
- CISA https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
- Node.js project on GitHub https://github.com/nodejs/node/releases/tag/v22.23.5
- Node.js project on GitHub https://github.com/nodejs/node/releases/tag/v24.22.3
- Node.js project on GitHub https://github.com/nodejs/node/releases/tag/v26.13.1
Change history
- — Published: Published 12 November 2026 from the Node.js umbrella announcement and release notices of 11 November 2026.
- — Correction: November 22, 2026: clarified source attribution for CVE-2026-123873 and CVE-2026-106071 across the nodejs.org Notable Changes pages, the GitHub release entries and the November 11 umbrella notice. Patch versions, affected ranges and guidance are unchanged.