Skip to main content
Exostruction
Back to overview
Alexander Kreitmair4 min read

Ubuntu kernel and Node.js: two critical updates to check this week

Ubuntu kernel flaw CVE-2026-98432 and 16 Node.js fixes from 11 November: what is patched and what operators need to check.

Guide
Ubuntu kernel and Node.js: two critical updates to check this week

Two security updates are due this week, and neither works on its own: for Ubuntu, the kernel fix for the critical TCP flaw CVE-2026-98432 only takes effect after a reboot. For Node.js, the project fixed 16 vulnerabilities on 11 November; the patched versions are 22.23.5, 24.22.3 and 26.13.1. Check what is actually running on each system, not just what is installed. Status as of 12 November 2026. Details follow on the Ubuntu kernel and on Node.js.

Installed does not mean active: a new kernel or a new Node.js version only protects you once the system is running it.

Ubuntu kernel: CVE-2026-98432

The flaw affects how the Linux kernel handles IPv4 TCP connections. According to Ubuntu it can lead to remote code execution and is rated critical at 9.8 under CVSS 3.1. By that rating, an attacker needs neither a login nor any action by a user. It was published on 15 October 2026, and the fix is in the kernel repository. Since 10 November, Ubuntu has been publishing the related security notices.

Status of the standard kernels according to the Ubuntu CVE page as of 11 November 2026:

UbuntuStatusPatched kernel
26.10patched7.3.0-10.10
26.04 LTSpatched7.0.0-43.43
24.04 LTSpatched6.8.0-149.149
22.04 LTSpatched5.15.0-203.213
20.04, 18.04, 16.04fix in progressstill open
14.04not affectednot needed

For some HWE kernels, such as linux-hwe-6.8 on 22.04 and linux-hwe-7.0 on 24.04, Ubuntu still lists the fix as in progress. If you cannot reboot right away, the Ubuntu page describes a stopgap using an nftables rule. Ubuntu itself says it lowers the risk but does not fully prevent exploitation.

Node.js: the 11 November security release

The Node.js project has published security releases for the 22, 24 and 26 lines. They fix 16 vulnerabilities: 7 high, 6 medium and 3 low severity. The libraries llhttp, undici and sqlite are updated as well. This makes the October release covered in our article on PHP2Shell and Node.js outdated.

The seven high-severity flaws at a glance:

TopicEffectLines
HTTP/2, session teardown (CVE-2026-123863)Server can be crashed without authentication24, 26
HTTPS, empty TLS write (CVE-2026-123864)Memory of other connections may become readable22, 24, 26
HTTP/2, protocol error during shutdown (CVE-2026-123865)Memory and file descriptors fill up22, 24, 26
HTTP/2, stream teardown (CVE-2026-123866)Freed memory may be sent to the peer22, 24, 26
TLS handshake (CVE-2026-126051)Server process can be terminated24, 26
TLS 1.2 renegotiation (CVE-2026-123872)Client certificate check can be bypassed22, 24, 26
HTTP/2, respondWithFile (CVE-2026-123874)Memory error, exploitable without authentication24, 26

Whether your application is actually affected depends on whether it provides HTTP/2, HTTPS or TLS server functions through Node.js itself. Some flaws require specific handler patterns. You should apply the update regardless. The project also states that versions that have reached end of life are affected by every security release.

What operators should check now

  1. Build an inventory. Where does Ubuntu run, where does Node.js? Think of servers, VMs, cloud instances, containers and old internal tools.
  2. Check the running version. uname -r shows the running kernel and node -v the Node.js version, each in the environment that serves requests.
  3. Kernel: update and reboot. On Ubuntu, the file /var/run/reboot-required indicates that a reboot is pending.
  4. Node.js: update and redeploy. The running process has to start with the new version.
  5. Separate containers. Containers use the host's kernel, so the host patches it. For Node.js, by contrast, the image has to be rebuilt and redeployed.
  6. Exposed systems first. Anything directly reachable from the internet takes priority.
  7. Ask your host and service provider. Was it patched, to which version, and when was it rebooted or redeployed?

Our practical view

As an IT service provider, we recommend taking three things away from this week. This is our assessment, not a vendor requirement:

  • Define maintenance windows in advance. Both updates need a step that is easy to postpone: a reboot or a new deployment. An agreed time slot prevents a fix from being installed but not active.
  • Clarify responsibility in writing. Anyone who runs or outsources a system should know who patches the kernel and the runtime. That belongs in the maintenance contract.
  • Keep several layers in view. Kernel, runtime and application are patched separately. The same pattern applies to gateways, see securing remote access.

For questions about inventory, patch processes and operations, our server infrastructure and IT consulting services can help.

Share

Frequently asked questions

  • No. The container image contains the Node.js version. It has to be rebuilt and redeployed, otherwise the container keeps running the old version.

  • No. The patched Node.js versions are now 22.23.5, 24.22.3 and 26.13.1. Our article on PHP2Shell and Node.js still lists the October versions.

  • Indirectly, yes. Containers share the kernel with the host, so the host has to be patched and rebooted. A new image does not change that.

Author of this article

AK

Alexander Kreitmair

Co-Founder & Infrastructure

Certified systems integration specialist. Makes sure the systems keep running - servers, networks, deployment pipelines.

This article is for general information only and does not replace individual legal, tax, or business advice. Prices, timelines, and assessments are non-binding estimates provided without guarantee.