Home › Articles › Linux flaw and Node.js patches: what a small office should do this week

Linux flaw and Node.js patches: what a small office should do this week

By DRAK Infinity · Updated November 12, 2026 · 4 min read
A Home lab beside a cracked shield mended with a wrench and a bandage, next to a locked door.
A patch applied, and no open door to find.

A serious Linux kernel flaw was fixed this fall, and on November 11, 2026, Node.js released sixteen security patches. Here is, in plain language, who is affected and what to do.

1. The Linux flaw (CVE-2026-98432)

  • What it is. A flaw in how Linux handles network connections, present since kernel version 4.4, so in almost every Linux server.
  • Its severity. Rated 9.8 out of 10 by the kernel’s CVE team. An attacker can trigger it remotely, without a password, by targeting an open, listening network port.
  • Where things stand. Red Hat released its fix on November 1; Ubuntu’s fix, first in testing in early November, is now available in the official archive for 22.04, 24.04, 26.04 and 26.10. A restart is required after updating.
  • Is it being exploited? No vendor or official body has reported a confirmed successful attack. A researcher has, however, observed Internet scans that resemble one.

2. The Node.js patches of November 11, 2026

Node.js runs a huge number of sites and tools, including n8n. Versions 26.13.1, 24.22.3 and 22.23.5 fix sixteen flaws, seven of them rated high severity: most let a stranger crash an exposed server (HTTP/2, TLS); another affects HTTPS servers and can, under certain conditions, leak memory, including private keys. Versions that no longer receive patches (including 20, already end of life) remain exposed.

3. Who is affected

  • Any Linux server reachable from the Internet: a website, a NAS with an open port, a camera, a home router.
  • Any tool built on Node.js and exposed on the Internet.
  • Your host takes care of it for a hosted website; just ask them whether it is done.

4. What to do, in four steps

  1. Update and restart your Linux machines. Then check with uname -r that the version has changed.
  2. Update Node.js and restart your services; node --version should show one of the three fixed versions.
  3. Close any open ports on your router that you do not need. It is this year’s most worthwhile move.
  4. Turn on automatic security updates, so you do not depend on the next headline.

5. Why our installations are barely exposed

A Home lab installed by DRAK Infinity opens no port on the Internet: you reach it through an encrypted tunnel, device by device. An attack that needs an open door does not find one. That does not excuse it from updates, which happen every night, automatically. No system is impossible to break into; it can, however, be stripped of its doors.

Not sure which ports are open at your place?

It is the first thing we check at the Diagnostic, by video call or at your place in Montréal and the surrounding area.

See the Home lab page

Sources: The Hacker News, Ubuntu’s security blog, the official Node.js announcement.