←Back to Knowledge

PHP, Node.js, Go and Linux all released security updates in October 2026. Here is the version that fixes each issue, and what to ask your web vendor.

Date
Reading
4 min read
Written by
Nick Li
Tags
#Risk#Web#Engineering

Most business owners never think about which version of PHP or Node.js their website runs on. That is fair: it is the kind of detail your web vendor or IT person should handle. But October 2026 has been an unusually busy month, and this time it is worth asking them directly.

Within one week, PHP, Node.js, Go and the Linux kernel all published security fixes, and at least one of the problems is already being attacked. Below we list each one with the exact version that fixes it, as of 23 October 2026. If you are not technical, skip to the end: there are four questions you can send to whoever looks after your website.

PHP: the urgent one

PHP runs WordPress and a large share of small business websites. On 21 October the PHP project fixed two critical flaws, nicknamed PHP2Shell (CVE-2026-109618 and CVE-2026-109619). They can let an attacker run their own code on a server without logging in. PHP's own security advisory asks every user to update immediately, and the security firm watchTowr reports attacks already under way, with attempts seen from 17 October.

  • PHP 8.5 → 8.5.12 or later
  • PHP 8.4 → 8.4.27 or later
  • PHP 8.3 → 8.3.36 or later
  • PHP 8.2 → 8.2.35 or later (8.2 itself stops receiving updates on 31 December 2026)
  • PHP 8.1 and older → no official release. Move to a supported version, or ask your hosting provider whether they have patched it.

On shared hosting, the provider usually updates PHP for you. Check anyway: the PHP version is normally shown in the hosting control panel.

Node.js: ten fixes in one release

Node.js runs many modern websites, online shops and internal tools. On 21 October it fixed ten vulnerabilities, four of them rated high. The most serious, CVE-2026-111497, is a memory bug in the code that unpacks Brotli-compressed data, and it can lead to remote code execution. Two others, CVE-2026-106069 and CVE-2026-105483, can let a fake server pass a certificate check.

  • Node.js 26 → 26.12.1 or later
  • Node.js 24 → 24.22.1 or later
  • Node.js 22 → 22.23.4 or later
  • Node.js 20 and older → past end of life, so no fix. Plan the upgrade.

We have not seen reports of these being attacked yet. Still, this is an update for this week, not this quarter.

Go: rebuild, not just update

Go is common in back-end services and command-line tools. Go 1.27.3 and 1.26.10, released on 19 October, fix a problem in how certificates are checked (the crypto/x509 package). The 8 October releases, 1.27.2 and 1.26.9, had already fixed security issues in net/http, crypto/tls, html/template and other packages.

  • Go 1.27 → 1.27.3 or later
  • Go 1.26 → 1.26.10 or later
  • Go 1.25 and older → no longer supported

One detail is easy to miss. A Go program carries its own copy of these libraries, so installing a new Go version on a developer's laptop changes nothing on the server. The program has to be rebuilt with the new version and deployed again.

Linux: mostly a job for your hosting provider

PwnEscape (CVE-2026-99999) is a bug in the network code of the Linux kernel. On a server that runs virtual machines, someone who controls one of those machines can read memory from the host underneath, and that memory may hold other customers' data. Red Hat rates it important and tracks it as an active-exploit case.

With Linux you normally do not choose a kernel version yourself. You install your distribution's update and restart the server. As of 23 October:

  • Debian 12 and 13 → fixed in linux 6.1.190-1 and 6.12.113-1 (Debian tracker)
  • Ubuntu 22.04, 24.04 and 26.04 → fix in progress, not released yet (Ubuntu)
  • Red Hat Enterprise Linux → fix in progress, no workaround

If you rent a VPS or cloud server, the host machine is your provider's responsibility. Updating your own server is still worth doing, because Red Hat notes that a local user can trigger the bug too.

Four questions for your web vendor

You do not need to understand every CVE number. Send these four questions to whoever looks after your website or systems:

  • Which versions of PHP, Node.js or Go do our website and systems run?
  • Are they on the fixed versions above? If not, when will they be?
  • Is our hosting provider patching the PwnEscape Linux flaw, and have our own servers been updated and restarted?
  • Is anything we use on a version that no longer gets security updates at all?

A slow answer to these questions tells you something too.

Sites with fewer moving parts have less to patch, which is one reason we often recommend static websites. If you are not sure what your systems run, or want a second opinion on the answers you get, get in touch.

Further reading