Node.js shipped security releases for its 22, 24 and 26 lines on November 11. The worst of the 16 fixes let an outsider with no account read memory from other connections on a Node HTTPS server, including private TLS keys and other users’ requests.
Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.
Node runs a lot of company web apps and APIs. Many of them live inside containers that nobody rebuilds unless asked, so updating the copy on a laptop doesn’t fix the one baked into production images.
Node.js fixed an HTTPS bug that can hand other users’ data, even TLS keys, to a stranger. Upgrade to 22.23.5, 24.22.3 or 26.13.1 and rebuild the containers.
The 5-Minute Cyber BriefDon’t Miss the Policy Changes That Affect Security Decisions
Get the key CISA actions, new regulations, guidance, and risk shifts in a quick daily brief.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Node.js fixes HTTPS and HTTP/2 bugs that leak memory to strangers
Seven of the fixes are rated high. Most sit in the HTTP/2 and TLS code, where two can leak memory and others let a remote client crash the server.
- HTTPS memory leak (CVE-2026-123864): an unauthenticated client can get the server to copy unrelated heap memory into a request body. It needs a handler that flushes headers before the body ends; plain http is not affected.
- HTTP/2 leak (CVE-2026-123866): tearing down a stream mid-write can send freed response memory to the peer.
- Crash (CVE-2026-123863): any client can abort a default HTTP/2 server on 24.x and 26.x.
- Client certificates (CVE-2026-123872): TLS 1.2 renegotiation lets a client switch hostnames and skip a stricter client-certificate rule on another host.
Node servers that speak HTTPS or HTTP/2 on 22.x, 24.x or 26.x
If your apps serve HTTPS directly from Node, or use HTTP/2, they are in scope. Apps behind a reverse proxy such as nginx that terminates TLS are less exposed to the TLS bugs, but the proxy setup varies, so check rather than assume.
The Node.js project did not report any attacks. None of these flaws is on CISA’s exploited list either, but the advisory explains how each bug is triggered, which shortens the work for anyone trying to reproduce them.
Upgrade to 22.23.5, 24.22.3 or 26.13.1 and rebuild your images
- Run
node -von servers and in each container image. Anything below 22.23.5, 24.22.3 or 26.13.1 needs the update. - Rebuild container and CI base images that pin an older Node version, then redeploy. A host update doesn’t change what is inside the image.
- Upgrade internet-facing HTTPS and HTTP/2 services first, then internal APIs.
- If you rely on per-hostname client-certificate rules, consider requiring TLS 1.3, which has no renegotiation, on those hosts until the upgrade is done.
Forward this
For whoever owns our web apps and APIs: Node.js released fixes for bugs that can leak other users’ data, including TLS keys, from Node HTTPS servers, and others that let anyone crash an HTTP/2 server. Can we check which services and container images run Node 22, 24 or 26 and get them onto the new releases this week?
Details
- CVE-2026-123864 (high): HTTPS zero-length TLS write re-enters llhttp, use-after-free and heap disclosure. 22.x, 24.x, 26.x.
- CVE-2026-123866 (high): HTTP/2 stream teardown sends freed response memory. CVE-2026-123863 (high): HTTP/2 remote abort, 24.x and 26.x. CVE-2026-123872 (high): TLS 1.2 renegotiation servername change bypasses client-certificate checks.
- Fixed: v22.23.5, v24.22.3, v26.13.1 (November 11, 2026). The release also updates llhttp, undici and sqlite.
- Exploitation: none reported by the Node.js project; not in CISA’s KEV catalog.
Hunt / verify
- Search Dockerfiles and CI files for
FROM node:tags that pin older versions. - Look for unexpected Node process restarts or crash loops on HTTP/2 services since November 11.
- If a public HTTPS service ran an affected version and echoes request bodies back to users, consider rotating its TLS private key.
Source: Node.js November 2026 security releases; The Hacker News
Sources
- Node.js: Wednesday, November 11, 2026 security releases
- The Hacker News: Node.js fixes 16 flaws, including HTTP/2 bugs that crash servers and leak other connections’ data
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.