What happened#
The Node.js project published its November 2026 security releases advisory, dated Wednesday 11 November 2026. It covers the three supported lines: 26.x, 24.x and 22.x. The page says the highest severity fixed is High on all three, and that the releases update bundled dependencies: llhttp on every line, undici on 24.x and 26.x, and SQLite on 22.x and 24.x.
Dates differ slightly between sources. The advisory says the releases land “on, or shortly after” 11 November. The Node.js download index dates 26.13.1 and 24.22.3 to 10 November and 22.23.5 to 11 November, and flags all three as security releases. The release page for v24.22.3 shows an 11 November tag time. Either way, all three are out.
The advisory credits several reporters. Five of the issues were reported by Chris Rohlf with Claude and Anthropic Research, and most of the fixes are credited to the maintainer mcollina. Others were reported by pimterry, Trail of Bits and individual researchers.
The 16 issues#
Here is every CVE the advisory lists, in its own order, grouped by severity.
| CVE | Severity | Affected lines | What it is |
|---|---|---|---|
| CVE-2026-123863 | High | 26.x, 24.x | HTTP/2 remote abort: a failed assertion in the HTTP/2 session destructor lets a remote client crash the server. A variant of CVE-2024-27983. |
| CVE-2026-123864 | High | 26.x, 24.x, 22.x | HTTPS re-entrancy: a zero-length TLS write re-enters the HTTP parser, causing use-after-free and out-of-bounds reads that can leak heap memory, including TLS keys, into response bodies. Needs a handler that calls res.flushHeaders() before the body ends and then res.end() with a non-empty chunk. Plain-text node:http is not affected. |
| CVE-2026-123865 | High | 26.x, 24.x, 22.x | HTTP/2 session leak during shutdown: a protocol error leaves sessions uncleaned, leaking memory and file descriptors. Remotely triggerable with a GOAWAY frame. An incomplete fix of CVE-2026-48937. |
| CVE-2026-123866 | High | 26.x, 24.x, 22.x | HTTP/2 teardown use-after-free: freed or other connections’ response memory can be written to the peer. |
| CVE-2026-126051 | High | 26.x, 24.x | Uncaught exception in TLS servers: deferred handshake callbacks don’t handle a socket destroyed before they run, so a crafted client hello followed by a FIN can crash the process. Applies when using SNICallback, OCSPRequest, newSession, resumeSession or server.addContext(). |
| CVE-2026-123872 | High | 26.x, 24.x, 22.x | TLS 1.2 renegotiation bypasses client-certificate authentication: a client can change the server name during renegotiation and carry its authentication to a host with a stricter policy. |
| CVE-2026-123874 | High | 26.x, 24.x | HTTP/2 use-after-free: resetting a stream during a pending write frees an Http2Stream that is still in use. Needs respondWithFile() or respondWithFD(). |
| CVE-2026-123828 | Medium | 26.x, 24.x | session.altsvc() heap overflow: a one-byte overflow when a long, valid origin is passed to Http2Session.altsvc(). |
| CVE-2026-123867 | Medium | 26.x, 24.x, 22.x | CA-only SNI contexts fail open: an SNI context with a CA but no server certificate silently falls back to the default client CA, bypassing per-host mutual TLS. |
| CVE-2026-123868 | Medium | 26.x, 24.x | Unbounded HTTP/2 queued data: inbound data on undrained streams isn’t charged to maxSessionMemory, so memory can grow far past the limit. |
| CVE-2026-123871 | Medium | 26.x, 24.x, 22.x | Proxy credentials in error messages: four ERR_PROXY_INVALID_CONFIG paths print the raw proxy URL with credentials. Missed by the fix for CVE-2026-48615. |
| CVE-2026-123877 | Medium | 26.x, 24.x, 22.x | https.Agent session reuse bypasses certificate validation: requests that omit ca and requests with ca: [] share a session-cache key. |
| CVE-2026-123875 | Medium | 26.x, 24.x, 22.x | Cancelling respondWithFile() downloads can crash the server (NULL dereference). |
| CVE-2026-123829 | Low | 26.x, 24.x, 22.x | Permission Model leak in recursive fs.watch on macOS and Windows: names of files in denied subdirectories are revealed, not their contents. |
| CVE-2026-123862 | Low | 26.x, 24.x, 22.x | zlib params() plus destroy() can throw an uncatchable internal assertion. Only for apps that call deflate.params() while streaming. |
| CVE-2026-106071 | Low | 26.x, 24.x, 22.x | Permission Model wildcard over-grant: a short path can match a longer wildcard grant, for example --allow-fs-read=/etc/passwd.* also allowing /etc/passwd. |
A small discrepancy: the release notes for v24.22.3 list a low-severity ID, CVE-2026-123873, that does not appear on the advisory page I read, and they don’t list CVE-2026-106071, which the advisory does. They also mention a Brotli update (1.2.1) that the advisory’s dependency list doesn’t. I’m treating the advisory as the authoritative list and flagging the difference rather than guessing at it.
Am I affected?#
This is about what your code, or a dependency, asks the Node.js runtime to do. Using the advisory’s own scope notes:
| If your app or a dependency... | Relevant CVEs | Worth checking |
|---|---|---|
| Runs an HTTP/2 server (node:http2), directly or through a framework or gateway | CVE-2026-123863, -123865, -123866, -123874, -123828, -123868, -123875 | This is the biggest group. Check whether anything on the public side of your stack terminates HTTP/2 in Node.js. |
| Runs an HTTPS server and flushes headers before ending the response | CVE-2026-123864 | The advisory says this needs the flushHeaders-then-end pattern. Plain-text node:http is not affected. |
| Runs a TLS server with SNI, OCSP or session callbacks, or uses client certificates or per-host mutual TLS | CVE-2026-126051, -123872, -123867 | These concern handshake handling and client-certificate policy. |
| Makes outbound HTTPS calls through https.Agent, or through a proxy | CVE-2026-123877, -123871 | Session reuse across different trust settings, and credentials in error messages. |
| Uses the Permission Model or recursive fs.watch, or calls zlib params() | CVE-2026-123829, -106071, -123862 | Low severity and niche. |
If you only run a front-end site behind a managed host and never run Node.js as a public HTTP/2 or TLS server yourself, several of these won’t apply directly. The advisory doesn’t say which hosts terminate HTTP/2 in Node.js, so I can’t tell you that for yours.
What to do now#
- Find out what you’re running, everywhere: your machine, CI, servers and every container image.
- Upgrade to 22.23.5, 24.22.3 or 26.13.1, matching your current line. The advisory lists no workaround.
- Rebuild, don’t just restart, anything that bundles its own Node.js. A container image keeps the runtime it was built with, so rebuild it from a patched base image.
- Move off end-of-life lines. The advisory says end-of-life lines are always affected by a security release and users should move to a supported, up-to-date version.
- Check your own server code for HTTP/2 use, the flushHeaders-then-end pattern, and SNI or session callbacks, so you know which rows of the table above matter to you.
# 1. What am I running, right now?
node -v
# 2. Upgrade with nvm (pick your line)
nvm install 24.22.3 && nvm alias default 24.22.3
nvm install 22.23.5
nvm install 26.13.1
# 3. Does my code run an HTTP/2 or TLS server itself?
grep -rnE "node:http2|from ['\"]http2|node:tls|SNICallback|flushHeaders" src/ app/ lib/ 2>/dev/null
# 4. Rebuilding a container? Bump the base image tag, then:
docker build --no-cache -t your-app .
docker run --rm your-app node -vHow I checked this site#
This site is a Next.js project. I searched its source, excluding node_modules, for direct use of the APIs these CVEs touch: node:http2, node:tls, https.Agent, respondWithFile, altsvc, fs.watch, zlib and the Permission Model flags, and found none. The repository has no engines field, vercel.json or .nvmrc, so it doesn’t pin a Node.js version itself. In the environment where I ran these checks, node -v reported v22.23.4, which is below the fixed 22.23.5. I haven’t verified which patch version a production host uses, so I’m not claiming anything about that. That covers this repository only. My earlier post on the October Node.js release has the previous round.
What the sources don’t say#
- Whether anyone is exploiting any of the 16 issues. The advisory doesn’t say.
- Which hosting platforms terminate HTTP/2 in Node.js, and when each will roll out the patched versions.
- How many real-world servers meet the preconditions, such as using respondWithFile() or the flushHeaders pattern.
- Why the release notes and the advisory differ on one low-severity ID and on the Brotli update.
- I did not read independent coverage of these specific fixes. My second source is the Node.js download index and the release notes for versions and dates.
My take#
My own opinion, not from the advisory.
Most of this release sits in the HTTP/2 and TLS layers, and two of the High items are described by the advisory as a variant of, or an incomplete fix for, earlier CVEs. For a developer, the practical lesson is to know where your stack terminates HTTP/2 and TLS. If it is a reverse proxy or a CDN, Node.js may never see those frames. If it is your own Node.js process, patching the runtime is the whole job, and a framework upgrade won’t help.
Sources#
- Node.js: November 11th 2026 Security Releases (primary source, also read in its repository form)
- Node.js: release notes for v24.22.3
- Node.js: download index (release dates and security flags)
- npm: undici package metadata (the registry lists undici 7.30.2, the version the v24.22.3 notes name, as published on 5 November)
Keep reading
7 min read
Hono advisories, November 2026 (CVE-2026-126355 to 126359 and more): what to upgrade to, and how to check your middleware
Hono 4.13.16 fixes five advisories: mount() and RegExpRouter middleware bypasses, a csrf() gap and a form validator skip. Plus two @hono/node-server fixes. What to check.
7 min read
Mongoose advisories, November 2026 (CVE-2026-125120 and four more): what to upgrade to, and how to check your queries
Five Mongoose advisories, one Critical (CVSS 9.8): sanitizeFilter was skipped on countDocuments and on the connection-level option. Patched versions and how to check.