Skip to content
senn-techsenn-tech
Back to blog
Security
Security and data protection2026-11-15· By Franz Senn

Node.js 24.22.3, 22.23.5 and 26.13.1: 16 CVEs and where our fleet stands

On 11 November 2026 the Node.js project released security fixes for three lines: 22.23.5, 24.22.3 and 26.13.1. The announcement lists 16 CVEs: seven High, six Medium and three Low. All seven High issues are in HTTP/2 or TLS. Node 20 does not appear in the announcement.

A Node security release replaces the runtime itself. Whatever Node ships, meaning HTTP/2, TLS and the HTTP parser, stays vulnerable until the binary inside the container image or on the host is swapped; updating npm packages changes nothing there. Whether a bug becomes a real risk depends on who speaks HTTP/2 or TLS to the client: Node itself, or a proxy in front of it.

Node.js logo
The Node.js project published the security releases on 11 November 2026 and describes the 16 CVEs in its announcement. (Quelle: Simple Icons (Repo CC0), trademark: Node.js Foundation)

What was fixed

Everything in this section comes from the announcement (verified: the page on nodejs.org read and compared with the Markdown source in the project's GitHub repo).

The seven High issues: CVE-2026-123863 (HTTP/2: a client can kill the server through a failing assertion, lines 24 and 26), CVE-2026-123865 (HTTP/2 sessions leak memory and file descriptors after a protocol error during shutdown), CVE-2026-123866 (tearing down a stream during a backpressured write can send freed heap memory to the peer), CVE-2026-123874 (use-after-free around respondWithFile(), lines 24 and 26), CVE-2026-123864 (HTTPS only: a zero-length TLS write re-enters the HTTP parser, giving a use-after-free and a heap read), CVE-2026-126051 (a remotely triggerable uncaught exception in TLS servers that use SNICallback, OCSPRequest, newSession, resumeSession or server.addContext(), lines 24 and 26) and CVE-2026-123872 (TLS 1.2 renegotiation lets a client change the server name and bypass per-hostname client certificate checks).

Line 22 is affected by eleven of the 16 entries, lines 24 and 26 by all of them. The announcement says nothing about exploitation and offers no workarounds. NVD lists CVE-2026-126051 as "Awaiting Analysis", with no score yet (read on 15 November).

What runs here

Measured on 15 November 2026 with the read-only script from our drift check: node -v on each host, plus docker ps and docker exec <container> node -v. 48 of 49 hosts answered; one timed out. Containers without a shell in the image stay invisible to this probe.

MeasureCountInstrument and date
Hosts with node in PATH27probe of 48 hosts, 15 Nov 2026
of those on a fixed version (16 × 24.22.3, 1 × 22.23.5)17same
of those below it (9 × 24.22.1, 1 × 22.23.4)10same
Containers with readable Node66 of 251docker exec, 15 Nov 2026
of those on a fixed version (3 × 24.22.3, 2 × 22.23.5)5same
of those below it, images without a registry path (heuristic)47 (44 × 24.22.1, 2 × 22.23.4, 1 × 24.22.2)same
of those below it, images with a registry path14 (8 × 22.23.4, 2 × 26.12.1, 2 × 24.22.1, 1 × 24.22.2, 1 × 24.11.1)same

"Fixed" means the version the announcement names for that line: 22.23.5, 24.22.3, 26.13.1. The split by registry path is a heuristic: official Docker Hub images such as node have no path in the name and therefore land in the group without a registry path, although we did not build them. The split does not say who built an image.

Node state of our fleet on 15 Nov 2026: on fixed version versus belowHosts on fixed version17 · 17Hosts below10 · 10Containers on fixed ver.5 · 5Containers below61 · 47 without, 14 with registry path070
Own measurement of 15 Nov 2026, only hosts with node in PATH (27) and containers with readable Node (66 of 251). Fixed version = 22.23.5, 24.22.3 or 26.13.1. (Quelle: own measurement, 15 Nov 2026)

Can the bugs reach our services?

We searched the working directory of the 66 readable containers, excluding node_modules, for createSecureServer, https.createServer and node:http2. That is a text search and proves nothing about runtime behaviour. It returned five hits, none in an application that demonstrably starts an HTTPS or HTTP/2 server itself. Two belong to a monitoring tool that can optionally start an HTTPS server; the container environment had no SSL variables. One belongs to an analysis tool that starts HTTPS only when a certificate path is set; it is not set in the container. One is in a folder of checked-out repositories that are not the running service. The fifth is a bundled HTTP client chunk.

What follows is derived, not proven: in the 66 searched containers the seven High issues have no entry point, as long as a reverse proxy terminates TLS and Node sits behind it speaking plain HTTP. Not searched are the 185 containers without readable Node and the Node installations on the 27 hosts with node in PATH; we say nothing about those. What remains are the dependency bumps in the same releases. The announcement lists llhttp (lines 22, 24, 26), undici (24, 26) and sqlite (22, 24) but attaches no CVE numbers to them. We did not look into what exactly they fix.

Which line, which version

The project's release schedule (read on 15 November) puts Node 20 at end of life since 30 April 2026. Node 22 has been in maintenance since 21 October 2025 and runs to 30 April 2027. Node 24 entered maintenance on 20 October 2026 and runs to 30 April 2028. Node 26 became LTS on 28 October 2026 and runs to 30 April 2029.

For this round: same line, new patch level. A move to line 26 would be a decision of its own and does not belong in a security patch.

  1. Move images we build ourselves to node:24.22.3. On 15 November the Docker Hub API gives the digest sha256:116b800c3754b440ee0aa3ed2f20f5bf3d99a554bfd9adeea09ea8017f6e85f5 for 24.22.3-alpine and sha256:dc26ae92c9fb15cf6b1d63e20f0944b2efe0f115b20e00be48fb23fceb061c54 for 24.22.3-slim. After the rebuild run docker exec <container> node -v and send one real request to the service; a running container proves nothing.
  2. Move derived images pinned to an older 22 release (22.23.4 in our case) to 22.23.5.
  3. Third-party images only after measuring: two containers already run 22.23.5, and Docker Hub shows the vendor image behind them updated on 12 November. For the other third-party images we have no fixed version measured yet; there the vendor's next image decides, and docker exec <container> node -v gives the answer.
  4. Hosts: put 24.22.3 into PATH wherever 24.22.1 is still installed.

A rush job exists only where Node itself terminates TLS or HTTP/2, for instance through https.createServer or http2.createSecureServer in the application. If that is you, do not wait for the next cycle.

We covered a similar case in October with the brotli flaw: Brotli hole in Node and Python, our fleet check. The hub Security and privacy collects our posts on patches and vulnerabilities. If you want your runtime versions checked, see our IT services.

Open points

  • A curl request from our workstation to nodejs.org got no connection, and we did not dig into why. We read the announcement through a page fetch and compared it with the Markdown source on GitHub.
  • The release notes of 22.23.5 list fixes for CVEs that the announcement says do not affect line 22 (for example CVE-2026-123863 and CVE-2026-123874). They include CVE-2026-123873 (heap snapshot in the permission model), which the announcement lacks, and leave out CVE-2026-106071. We did not resolve this and rely on the announcement for who is affected.
  • Node is readable in only 66 of 251 containers. One host was unreachable.
  • The text search for HTTPS and HTTP/2 servers does not cover node_modules or start flags such as --experimental-https. It covers only the 66 readable containers, not the other 185 and not the host installations.
  • Whether third-party images already carry a fixed version we measured for one image only. No second, independent rating (CVSS) was available on 15 November.

Read next: Composer 2.11 and its waiting period for new packages · two CVSS 10 flaws in GitLab · the ImageMagick policy against ImageTragick2 · the Brotli flaw in Node and Python: fleet check · the npm supply chain and a GitLab regex flaw

Further Reading

Questions?
Which Node.js versions fix the 11 November 2026 vulnerabilities?+

Node.js 22.23.5, 24.22.3 and 26.13.1. The announcement does not mention Node 20, which the release schedule lists as end of life since 30 April 2026.

Does an npm update close these holes?+

No. The bugs sit in the Node runtime itself, in HTTP/2, TLS and the HTTP parser. The fix is in place only once the Node binary inside the container image or on the host has been replaced.

Are services behind a reverse proxy such as Caddy affected?+

The seven High issues are in Node's own HTTP/2 and TLS code. If a proxy terminates TLS in front and talks plain HTTP/1.1 to Node, an attacker has no way in at those points. That holds only while the service itself starts no HTTPS or HTTP/2 server.