Erkan Ozdogan.
Security

Who shipped what, and when: how the October 2026 fixes travelled from upstream to your stack

9 min readTürkçe oku

Last updated:

Who shipped what, and when: October 2026 patch tracker

A security fix is not one event. It is published upstream, then rebuilt by distributions, then repackaged by hosting platforms, then baked into container images and libraries, and only then does it reach the process that serves your users. In October 2026 that chain was tested hard: PHP2Shell, a Node.js release, four BIND fixes, a Java alert and a compromised certificate authority all landed within a week. This post follows those fixes layer by layer, with the dates each layer shipped, so you can see where your stack sat in the queue and how to check it yourself.

TL;DR

  • Upstream projects shipped on day zero; the slowest layers were Linux distributions, some of which still had no BIND or Java fix eight days later.
  • Hosting platforms were among the fastest: cPanel and CloudLinux shipped PHP2Shell fixes on 21 October, and Imunify360 pushed WAF rules within hours.
  • Container images and language runtimes moved in one to seven days: Temurin on 22 October, Corretto on 23 October, Docker’s node images rebuilt on 28 October.
  • Every layer verifies differently: upstream by version, distributions and panels by package release or changelog, images by rebuild date, libraries by lockfile.
  • The fastest fix is useless until the running process restarts, so the last layer is always yours.

How does a fix travel through the layers?

How many days each layer tookDAY 0 = 21 OCTOBER 2026, STATUS ON 29 OCTOBERDAY -4-3-2-1DAY 01234567DAY 8UPSTREAMDISTRIBUTIONSHOSTINGIMAGES AND RUNTIMESPHP, Node, BINDOracle CPUPHP errataca-certsbrotliBIND: opencPanel, CloudLinux, ImunifyCL 8.4.27-1, KC EL10KC EL9certifiTemurinCorretto.NETDocker nodeSTILL OPEN: BIND, RHEL OpenJDK, KC EL8
How many days each layer took to ship the October 2026 fixes, from upstream projects to distributions, hosting platforms and images

Think of five layers. Upstream projects such as PHP, Node.js, ISC and Oracle publish the fix. Operating system distributions such as Red Hat, AlmaLinux, Debian and Ubuntu rebuild it into their packages, often as a backport. Hosting platforms such as cPanel and CloudLinux repackage it for their own PHP and Node.js builds. Container images and language ecosystems pick it up in base images, JDK distributions and libraries. And finally your deployment has to rebuild, redeploy and restart. Each hand-off adds time, and each layer has its own way of telling you the fix is there.

Layer 1: what did the upstream projects ship?

Project Date Fixed versions Since then
PHP 21 October 8.2.35, 8.3.36, 8.4.27, 8.5.12 CISA KEV on 26 October; separate unpatched CVE-2026-115560 announced 23 October
Node.js 21 October 22.23.4, 24.22.1, 26.12.1 24.22.2 and 26.13.0 (LTS) on 28 October
ISC BIND 21 October 9.20.30, 9.21.27 No exploitation reported
Oracle Java 20 and 21 October 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5, 27.0.1 Security Alert CVE-2026-91403 for eMudhra trust
Linux kernel Patch posted 22 October Not confirmed merged No CVE ids assigned by 29 October

Upstream is the easiest layer to verify because the version number is the fix. If you build PHP or Node.js yourself, or use the official binaries, comparing the version is enough. Two details changed during the week: PHP2Shell moved from “critical” to “known exploited” on 26 October, and PHP announced CVE-2026-115560, an upload progress issue the October releases do not fix, so the mitigation session.upload_progress.enabled = 0 stays relevant even on patched builds.

Layer 2: how fast did the Linux distributions follow?

Distributions were the slowest and least even layer, and the speed depended on the component more than on the vendor.

  • PHP. Red Hat published errata for RHEL 8, 9 and 10 PHP streams on 21 October, and AlmaLinux mirrored them the same day. Debian fixed bookworm and trixie, and Ubuntu released USN-8948-1 on 21 October. RHEL 9’s php:8.4 module was still listed as affected on 29 October.
  • Brotli. The system brotli library, which carries the same decoder bug as Node.js CVE-2026-111497, was fixed on RHEL and AlmaLinux on 26 October.
  • CA certificates. AlmaLinux released critical ca-certificates errata on 22 and 23 October, and Debian and Ubuntu removed the emSign ECC Root CA – G3 in their updates.
  • BIND and Java. These were the laggards. On 29 October RHEL, AlmaLinux and Ubuntu had no BIND fix, Debian had fixed only trixie, and Red Hat listed its OpenJDK fixes for CVE-2026-91403 as deferred.

Distribution packages almost never carry the upstream version number after a backport, so php -v or named -v tells you little. Verify by the package release against the advisory, or by grepping the changelog for the CVE id.

Layer 3: what did cPanel, CloudLinux and Imunify ship?

Hosting platforms moved faster than most distributions, because a shared hosting server without a PHP fix is exposed for every customer at once.

Vendor What shipped When How to verify
cPanel EasyApache 4 25.91: ea-php74 to ea-php85 fixed; 25.92: ea-nodejs22 22.23.4 21 October Package changelog lists the CVE ids
cPanel and WHM Internal PHP fixed in 138.0.18, 136.0.50, 134.0.66, 110.0.153 21 October /usr/local/cpanel/version
CloudLinux ea-php Backports with old numbers (e.g. 8.4.26-2), then php.net numbers (8.4.27-1) 21 and 23 October Changelog grep for the CVE id
CloudLinux alt-php CloudLinux 7, 8, 9 and Ubuntu 22.04 in stable; CloudLinux 10 via TuxCare ELS 21 and 22 October Package version against the CloudLinux post
Imunify360 WAF rulesets 8.83 to 8.88 21 to 23 October Ruleset version in the Imunify360 dashboard
KernelCare Live patch for the leaked networking bug: EL10, then EL9; EL8 ready 23 and 26 October kcarectl --patch-info

One detail is worth repeating for developers who deploy onto shared or managed hosting: a backported panel build can report the old PHP version while being fully patched. A health check that compares PHP_VERSION with 8.4.27 will report a false alarm on such a server, and a check that accepts any 8.4 build will miss an unpatched one.

Layer 4: what about Docker images, JDKs and libraries?

  • Docker node images. The 22.23.4 Alpine tags were pushed on 21 and 22 October, the Debian-based tags were rebuilt on 28 October, and the 24.22.2 tags followed late on 28 October.
  • JDK distributions. Eclipse Temurin shipped 17.0.21, 21.0.13 and 25.0.5 on 22 October; Temurin 8 and 11 had not appeared by 29 October. Amazon Corretto shipped on 23 October and rebuilt on 26 and 27 October.
  • Python. certifi released new bundles on 18, 20 and 23 October; the 2026.10.19 release dropped only the G3 root after the first release removed more, and pip 26.2.2 vendors it.
  • Other runtimes. Go 1.27.3 and 1.26.10 added an x509 block for the compromised intermediates, and Microsoft shipped out-of-band .NET updates on 25 October for the shared Brotli bug.

This layer is where most application teams actually receive fixes, and it is also where stale artifacts hide: an image built on 20 October, a lockfile pinned to an old certifi, a CI runner with its own JDK.

How long did each layer take?

Layer Fastest Slowest by 29 October
Upstream Day 0 for every project Kernel fix posted, merge not confirmed
Distributions PHP errata on day 0 (RHEL, AlmaLinux, Ubuntu) BIND and RHEL OpenJDK still open after 8 days
Hosting platforms cPanel, CloudLinux ea-php and Imunify rules on day 0 KernelCare EL8, CloudLinux 6 alt-php
Images and runtimes Temurin on day 1, Corretto on day 2 Temurin 8 and 11 still missing
Your deployment As fast as your rebuild and restart Whatever is never restarted

Find your layer

Pick what your service runs on to see where its fix stands and how to verify it:

A field note: the same fix, three answers

On our own cPanel servers the PHP2Shell fix arrived through EasyApache 4 on the afternoon of 21 October, without anyone running an update by hand. When we checked several days later it was still the backported build, ea-php84 8.4.26-2, even though CloudLinux had published a php.net-numbered 8.4.27-1 on 23 October. On that server three sources give three answers: php -v says 8.4.26, the package changelog lists both CVEs, and any scanner that compares versions with 8.4.27 would call it vulnerable. Only the changelog is right. When you build a dashboard for patch status, decide per layer which source it trusts.

What should a team do with this?

  1. Map each service to its layer. Write down where every runtime comes from, so you know whose release you are waiting for.
  2. Verify the way the layer publishes. Version for upstream builds, package release or changelog for distributions and panels, rebuild date for images, lockfile for libraries.
  3. Keep mitigations until the slowest layer arrives. For BIND, disable unused GSS-TSIG; for PHP, keep upload progress off; for the kernel, keep the namespace limit.
  4. Rebuild on a schedule, not only in emergencies. Weekly rebuilds from fresh base images turn a seven-day image lag into a non-event.
  5. Restart what you patched. The last layer is the running process, and it only changes when it restarts.

For the developer view of the bugs themselves, see PHP2Shell for developers and one compromised CA, many trust stores.

The short version

October 2026 showed that “patched” is a property of a layer, not of a vulnerability. The same fix was available upstream on day zero, on a cPanel server the same afternoon, in a Docker image a week later, and in some distributions not yet at all. Knowing which layer your service depends on, and how that layer proves a fix is present, is what turns a security release into a routine deployment.

FAQ: the October 2026 patch tracker

Which layer was slowest to ship the October 2026 security fixes?

Linux distributions, for some components. On 29 October RHEL, AlmaLinux and Ubuntu still had no BIND fix and Red Hat listed its OpenJDK fixes as deferred, while upstream projects and hosting platforms had shipped on day zero.

Were Docker’s official Node.js images rebuilt after the October 2026 release?

Yes. The 22.23.4 Alpine tags were pushed on 21 and 22 October, Debian-based tags were rebuilt on 28 October, and 24.22.2 tags followed the same day. Rebuild your images with --pull to pick them up.

Temurin vs Corretto: which shipped the October 2026 Java fixes first?

Temurin shipped 17, 21 and 25 on 22 October, and Corretto shipped on 23 October with rebuilds on 26 and 27 October. Temurin 8 and 11 builds had not appeared by 29 October, so Corretto was the faster option for those lines.

Why can a health check report a patched cPanel server as vulnerable?

Because backported packages keep the old version number. CloudLinux’s ea-php84 8.4.26-2 is patched but reports 8.4.26, so a check that compares versions with 8.4.27 raises a false alarm. Check the package release or changelog instead.

Which certifi version handles the eMudhra compromise correctly?

Use 2026.10.19 or later. The first release on 18 October removed all emSign roots and 2026.10.19 restored the unaffected ones, dropping only the G3 root. pip 26.2.2 vendors that release.

Does Node.js 24.22.2 add new security fixes on top of 24.22.1?

Its release notes list V8 backports and a stream fix, without new CVEs. The October security fixes are already in 24.22.1, so 24.22.2 is the better baseline rather than an emergency update.

Which other software shipped fixes for the October 2026 Brotli decoder bug?

The same decoder is embedded elsewhere: RHEL and AlmaLinux fixed the system brotli library on 26 October, Microsoft shipped out-of-band .NET updates on 25 October, and PHP’s Windows builds were rebuilt with Brotli 1.2.1.

Imunify360 WAF rules vs a patched PHP: what is the difference in October 2026?

The WAF rules from 8.83 to 8.88 block known exploit tools and patterns at the web server, while the patched PHP removes the bug. CloudLinux states that no rule covers the out-of-memory path of CVE-2026-109618, so only the patch is a fix.

How can teams track a kernel fix that has no CVE number yet?

Follow the vendor’s advisory for the report number, here ZDI-CAN-33367, and the live-patch status from your provider. AlmaLinux shipped kernels on 28 October and KernelCare covered EL10 and EL9 without waiting for a CVE.

How often should container images be rebuilt to avoid slow security fixes?

At least weekly from fresh base images, plus on demand for critical advisories. A scheduled rebuild means a fix that reaches the base image on day seven reaches production on day seven, not months later.

Sources