Security· Security Disclosure

PHP's October 2026 Critical RCEs: CVE-2026-109618 and CVE-2026-109619

PHP fixed two critical unauthenticated RCEs in 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Attackers chain them with a Linux kernel bug to get root: patch both now.

Atlas Security
Security Advisories
26 min read · 5,556 wordsUpdated November 3, 2026, 11:05 PM CST
Trevor Fannin@trevorfanninFounder, AtlasSecurity alerts and CVE breakdowns, plus infrastructure and general tech.Followon X (opens in a new tab)

Overview

PHP released fixes on October 21, 2026 for two critical vulnerabilities, CVE-2026-109618 (opens in a new tab) and CVE-2026-109619 (opens in a new tab), known together as php2shell. Both allow unauthenticated remote code execution (RCE), and both are rated CVSS v4.0 9.2. The fixed releases are 8.5.12, 8.4.27, 8.3.36, and 8.2.35. The bugs are in PHP itself — in the request setup and cleanup that wrap every script — and PHP says every installation that serves web requests is at risk. Its verdict: "there are no complete mitigations, updating is the only safe choice."

Why it's urgent: PHP is the server-side language of about 69% of websites (opens in a new tab) whose language is known (W3Techs). The details leaked two days before the planned disclosure, proofs of concept are circulating, and CISA added both CVEs to its KEV catalog on October 26. Attackers now chain them with a Linux kernel bug to get root, and Palo Alto Networks reports active exploitation against PAN-OS management interfaces. See the timeline.

Key facts

FieldDetail
CVEsCVE-2026-109618, "RCE via OOM corruption" (GHSA-w8hw-w9fx-j79w) · CVE-2026-109619, "RCE via stale global state" (GHSA-6wmf-4rv5-p3rp)
SeverityCritical — CVSS v4.0 9.2 for both, per PHP (AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H). Red Hat rates both Important on RHEL; see risk by server API.
WeaknessMemory corruption in request memory handling: use-after-free (CWE-416), plus CWE-755, CWE-824, CWE-1325, and CWE-1419
ImpactUnauthenticated RCE as the web server's user, from both, and root where the Linux kernel lacks the fix for CVE-2026-46300 (how). CVE-2026-109619 can also disclose worker memory. PHP built working exploits; mod_php is the demonstrated case.
Fixed in8.5.12 · 8.4.27 · 8.3.36 · 8.2.35 (all Oct 21, 2026)
No official fix8.1 and older (end-of-life). PHP published source-only backports for 8.1, 8.0, and 7.4.
Not fixed yetCVE-2026-115560, a related session upload progress issue that PHP will fix in its next regular release. Until then, PHP suggests session.upload_progress.enabled=0 (details).
ExploitationExploited in the wild, per watchTowr and Palo Alto Networks. Chained with CVE-2026-46300 to get root, per CISA and Dream. Proofs of concept circulating, per CERT-EU.
CISA KEVBoth added October 26, 2026. Federal civilian agencies must remediate by October 29 and run a forensic triage, under BOD 26-04 (opens in a new tab). The kernel's CVE-2026-46300 was added October 28 for the chain, due October 31. Known ransomware use: "Unknown" for all three (as of 11:05 PM CST, November 3).
CVE recordsPublished on cve.org (opens in a new tab). NVD (opens in a new tab) adds its own CVSS v3.1 scores: 9.8 for CVE-2026-109618 and 8.1 for CVE-2026-109619
CreditReported by Wiz, OpenAI, and Ryan at Calif.io; fixed by Arnaud Le Blanc, Ilija Tovilo, Jakub Zelenka, and Nora Dossche (per PHP's CVE records)

Who is affected

Any PHP that serves web requests is affected unless it runs the fixed build for its branch. The server API it runs under changes how exposed it is; that's covered further down.

BranchStatus on Oct 21, 2026Fixed inSecurity support until
8.5Active support8.5.12Dec 31, 2029
8.4Active support8.4.27Dec 31, 2028
8.3Security fixes only8.3.36Dec 31, 2027
8.2Security fixes only8.2.35Dec 31, 2026
8.1End-of-life (Dec 31, 2025)source backport only—
8.0End-of-life (Nov 26, 2023)source backport only—
7.4End-of-life (Nov 28, 2022)source backport only—
7.3 and olderEnd-of-lifenothing—

End-of-life branches are affected, back to PHP 5.4 at least. Wiz (opens in a new tab), one of the reporters, says every PHP version released in the last decade is affected by at least one of them, "going back to version 5.4," and Google Cloud's bulletin (opens in a new tab) lists "all PHP versions between 5.4 and 8.5." CERT-EU (opens in a new tab) lists "end-of-life branches (PHP 8.1 and older)" among the affected products, and NVD's records mark every version before 8.2.35 as vulnerable. Red Hat lists RHEL 6's PHP 5.3 as affected by both CVEs. It lists RHEL 7's PHP 5.4 as affected only by CVE-2026-109619, which it has fixed for Extended Life Cycle Support subscribers (RHSA-2026:88693). An appliance or legacy server still running PHP 5.x or 7.x should be treated as vulnerable. PHP 8.6 is still in release-candidate testing; the advisories cover only the stable branches, but 8.6.0 RC4 (opens in a new tab), released October 21, carries the fixes.

PHP inside other products. PHP also runs inside appliances, network devices, management interfaces, and commercial software, often where you can't update it yourself. Those need the vendor's fix, and that's where the most serious attacks reported so far have landed. Dream's report (opens in a new tab) describes rooted Palo Alto Networks firewalls on the PAN-OS 12.1 and 12.2 branches, and says "PAN-OS uses PHP 8.0.30," an end-of-life branch. Vendor advisories, as of 11:05 PM CST, November 3:

  • Palo Alto Networks (opens in a new tab): PAN-OS on PA-Series and VM-Series firewalls and on Panorama is affected through "the management web interface, which includes the HTTPS web UI and XML API service," and through dataplane interfaces with a management profile attached. Palo Alto reports "Active exploitation … targeting the Palo Alto Networks management interface exposed to the internet." It lists hotfixes as released for every supported branch from 10.2 to 12.2, and says the risk "is minimized by restricting access to the management interface to only trusted internal IP addresses." Its FAQ says "Current analysis shows no impact of CVE-2026-115560 on PAN-OS (NGFW and Panorama)."
  • Cisco (opens in a new tab) lists as affected: Expressway (fixed in 15.5.21), Duo Access Gateway (3.2.0), Ultra-Reliable Wireless Backhaul (Unified Industrial Wireless Software 26.2.1.9, expected November 2026), and ISE Portal Builder ("Fix deployed, no customer action required").
  • Fortinet (opens in a new tab): FortiOS, FortiManager, and FortiWeb are confirmed not affected. FortiDDoS and FortiSOAR are still under investigation.

CERT-EU recommends the NCSC-NL php2shell repository (opens in a new tab) for identifying third-party software that embeds PHP.

How the vulnerabilities work

A PHP web server keeps a pool of long-lived worker processes, and each worker handles many requests in turn. Every request gets its own memory. When a request ends, PHP frees that memory and resets the worker for the next one. Both vulnerabilities break that cleanup:

  • CVE-2026-109618: when a request runs out of memory, PHP abandons it on the spot. If that happens while PHP is still setting the request up — parsing a file upload, for example — the cleanup treats half-built data as valid and corrupts memory.
  • CVE-2026-109619: when a request dies from a fatal error, some of the worker's internal state can keep pointing at memory that has already been freed. The next request on that worker uses it.

An attacker can trigger either bug with crafted HTTP requests and no login. On Apache's mod_php, PHP demonstrated the attack with an unauthenticated request that triggers it before any application code runs, so the application or framework you use doesn't change your exposure. PHP's team turned both bugs into working exploits: code execution with the privileges of the web server's account, which typically reaches everything that account can read — application code, configuration files, database credentials, and API keys. Attackers are chaining that foothold with a Linux kernel bug to become root (below).

CVE-2026-109619 can also leak memory without running any code. PHP lists memory disclosure among its confirmed impacts, and Wiz warns that worker memory "may contain passwords, authentication tokens, API keys and certificates belonging to other requests or the server itself."

One commit, "Avoid state corruption via bailout," fixes both, so a single update covers both CVEs.

CVE-2026-109618: out-of-memory corruption

PHP enforces memory_limit by aborting the request with a longjmp() the moment an allocation would exceed it. In a few places, request state is reachable but not fully initialized when that jump happens, and the failing allocation needn't be related to it. Request shutdown then reads, branches on, or frees the half-built state, and that memory may still hold attacker-controlled data from earlier allocations. PHP says an attacker can force the out-of-memory condition on demand with crafted multipart (file-upload) requests, and it demonstrated complete RCE over HTTP against mod_php with default input and memory limits.

The fix stops using longjmp() for out-of-memory. PHP now ends the request with a graceful "soft" bailout at a safe point, and keeps a hard exit at a higher threshold.

CVE-2026-109619: stale global state

Some state that belongs to the worker — error, session, object, and extension state — points into memory owned by the current request, and must be reset before that memory is freed. A fatal error (an uncaught error, Maximum execution time exceeded, or out-of-memory) can cut an operation short before its reset runs, or a late diagnostic can repopulate error state after it was cleared. Either way, the pointer outlives its memory, and the next request on the same worker reads it before initialization resets it: a use-after-free that a crafted heap layout turns into RCE.

Exploitation takes two requests on one worker: one that leaves stale state behind, and a later one that touches it early. PHP confirmed two such early operations: diagnostics raised while applying invalid or deprecated INI settings, and session upload progress, which is enabled by default and runs without your code ever calling session_start(). PHP 8.5's fatal-error backtraces are the strongest case and the basis of the confirmed mod_php RCE; the session-upload-progress path was validated against both mod_php and PHP-FPM.

Chained with a Linux kernel bug

PHP2Shell runs the attacker's code as the web server's account. CVE-2026-46300 (opens in a new tab), known as Fragnesia, takes it the rest of the way. It's a local privilege escalation in the Linux kernel's IPsec code (XFRM ESP-in-TCP), a variant of the "Dirty Frag" bugs disclosed in May. Red Hat says it "allows a low-privileged local attacker to write arbitrary bytes into the page cache of read-only files, including sensitive system files. An attacker can exploit this to overwrite privileged binaries and gain root privileges." CISA's KEV entry says it "can be chained with CVE-2026-109618 and CVE-2026-109619 to implant PHP webshells and run commands as root."

In the campaign Dream describes, the PHP exploit's final request also ran the kernel exploit, which changed a PAM configuration file in memory so that su granted root without a password.

  • Severity: CVSS v3.1 7.8 from the kernel's CNA, NVD, and Red Hat. Red Hat rates it Important "because exploitation requires local access," and Ubuntu rates it High: "Trivial local privilege escalation." PHP2Shell supplies the local access. Ubuntu adds that an attacker could "possibly escape a container," and containers share the host's kernel.
  • Fixed upstream on May 23, 2026, in 5.10.257, 5.15.208, 6.1.174, 6.6.141, 6.12.91, 6.18.33, and 7.0.10, and in 7.1. The bug dates to Linux 3.9. Ubuntu's notes say kernels older than 5.6, such as 20.04's 5.4, lack a module the public exploits need and "are not affected in practice." Red Hat lists RHEL 6 and 7 as not affected.
  • The change lives in memory. Wiz: "The modification exists only in page cache memory and does not alter the on-disk binary." A reboot clears it, and the evidence with it, so run the compromise checks before the kernel reboot.
  • A proof of concept has been public since the bug's disclosure on May 13, per Wiz and Debian's tracker.

The kernel fix closes this path to root. It does nothing for PHP, so patch both.

Risk by server API (SAPI)

A server API, or SAPI, is the layer that connects PHP to whatever passes it web requests: a module inside Apache (mod_php), a pool of FastCGI workers behind nginx, Apache, or Caddy (PHP-FPM), a CGI binary (php-cgi), LiteSpeed's own PHP processes (LSAPI), or an application server with PHP built in (FrankenPHP). The SAPI controls how workers start, get reused, and clean up between requests — exactly where both bugs live — so it changes how exposed you are. The command-line php you run in a terminal or cron job is a SAPI too, but it doesn't serve web requests and isn't the concern here.

Every web SAPI needs the update. PHP's advisories rank the risk:

Server APICVE-2026-109618CVE-2026-109619
Apache mod_phpConfirmed RCEConfirmed RCE
PHP-FPMSuspectedConfirmed RCE, application-dependent
FrankenPHPLikelyNot shown in the default configuration
LiteSpeedLikelyConditional
php-cgiNamed at riskNamed at risk
  • mod_php is the worst case. It runs request shutdown unconditionally, so a request that fails during startup still reaches the vulnerable cleanup, "entirely before any application-specific code begins execution."
  • PHP-FPM is less proven, not safe. PHP calls it "susceptible" to CVE-2026-109618 by source analysis, without a complete exploit, and validated a working exploit for CVE-2026-109619 on a normal dynamic pool — one that "depends on a suitable application operation."
  • FrankenPHP also runs shutdown unconditionally, "analogous to Apache mod_php." PHP didn't show the second bug in its default configuration, but adds that "this does not make this environment immune." LiteSpeed "models FPM," with exploits for the first bug "likely but unvalidated," and is a conditional candidate for the second because it can apply special INI values early.

Red Hat rates both CVEs Important rather than Critical on RHEL. For CVE-2026-109618, it explains that standard RHEL deployments use PHP-FPM rather than mod_php, and "PHP-FPM workers exit on early initialization failures before reaching the corrupted structures, so remote code execution is difficult in practice and typically requires non-default behavior." Red Hat still describes FPM as reachable "through application-stage paths" for both bugs. A lower rating isn't a reason to wait.

How to check your systems

Check every place PHP runs, not just the host you're logged into. A machine can run a patched php on the command line while a container on it serves an old php:8.2-fpm image.

Check the PHP version and SAPI serving your site

Shell
php -v                                     # the command-line PHP, not necessarily the web's# The FPM binary's own versionphp-fpm8.3 -v                              # Debian/Ubuntu (the name matches the branch)php-fpm -v                                 # RHEL and most container images# Is Apache running mod_php?apache2ctl -M 2>/dev/null | grep -i php    # Debian/Ubuntu: "php_module" means mod_phphttpd -M 2>/dev/null | grep -i php         # RHEL and derivatives# Which PHP processes are running?ps aux | grep -E 'php-fpm|lsphp|frankenphp|php-cgi' | grep -v grep

php -v and php -i describe the command-line build, which can differ from the one serving your site. The most reliable read of the web side is a temporary phpinfo() page: its "Server API" line says "Apache 2.0 Handler" for mod_php or "FPM/FastCGI" for FPM, next to the "PHP Version." Delete it as soon as you've read it — phpinfo() exposes the configuration details attackers look for. And php-fpm -v reads the binary on disk: workers started before an update keep running the old code until you restart them.

Check distribution packages

Shell
# Debian / Ubuntudpkg -l | grep -E '^ii' | grep -E 'php|mod-php'apt list --upgradable 2>/dev/null | grep -i php# RHEL and derivatives, Fedorarpm -qa | grep -E '^php'dnf updateinfo list --cve CVE-2026-109618   # if the vendor ships CVE metadata

Then confirm against the distribution's security tracker:

PHP said distributions "received the patches in advance." Where they stood at 11:05 PM CST, November 3:

Ubuntu

CriticalFixedTracker
  • Every supported release
    Fixed
  • 14.04 – 20.04Through Ubuntu Pro
    Fixed
    14.04's PHP is 5.5

Debian

Partly fixedTracker
  • 13 "trixie"
    Fixed
    8.4.27-1~deb13u1
    DSA-6574-1
  • 12 "bookworm"
    Fixed
    8.2.35-1~deb12u1
    DLA-4848-1
  • Testing "forky"
    Fixed
    8.4.27-1
  • Unstable
    Fixed
    8.4.27-1
  • 11 "bullseye"php7.4
    Out of support
    Not in Debian's tracker for these CVEs

Debian 11 left LTS on August 31, 2026.

Red Hat

ImportantPartly fixedCVE page
  • RHEL 10
    Fixed
  • RHEL 9Base php
    Fixed
  • RHEL 9php:8.2 and php:8.3 streams
    Fixed
  • RHEL 9php:8.4 stream
    Affected
  • RHEL 8php:7.4 and php:8.2 streams
    Fixed
  • RHEL 7PHP 5.4
    Fixed
    RHSA-2026:88693
  • RHEL 6PHP 5.3
    Affected

Red Hat lists RHEL 7's PHP as affected only by CVE-2026-109619, and has fixed it for Extended Life Cycle Support subscribers.

Third-party repositories differ:

  • Ondřej Surý's repositories — packages.sury.org (opens in a new tab) for Debian 11, 12, and 13, and ppa:ondrej/php (opens in a new tab) for Ubuntu 22.04 and 24.04 — published October 21 builds of every branch from 7.4 to 8.5. The 7.4 and 8.2 changelogs we checked cite both CVEs. For Debian 11 hosts, which Debian no longer covers, it was the only packaged fix we found.
  • rpms.remirepo.net had no update on release day, by PHP's account. It published (opens in a new tab) 8.2.35, 8.3.36, 8.4.27, and 8.5.12 RPMs for Fedora 43 and later and Enterprise Linux 8 and later on October 22.

Check the Linux kernel

Every Linux host that runs PHP, including container hosts and Kubernetes nodes, needs a kernel with the fix for CVE-2026-46300, and that kernel has to be the one running.

Shell
uname -r                             # the running kerneluname -v                             # Debian: the package version runningdpkg -l 'linux-image*' | grep ^ii    # Debian/Ubuntu: installed kernel packagesrpm -q kernel                        # RHEL and derivatives: installed kernelsneeds-restarting -r                  # RHEL (dnf-utils): is a reboot needed?

If the installed kernel is newer than the running one, the fix isn't active until you reboot. Containers run on the host's kernel: uname -r inside one reports the host's, and a new image doesn't change it. We ran these on a Debian 12 host and in a Rocky Linux 9 container. Compare against your distribution's tracker (Debian (opens in a new tab) · Ubuntu (opens in a new tab) · Red Hat (opens in a new tab)). As of 11:05 PM CST, November 3:

  • Debian had fixed bookworm in 6.1.174-1 (DSA-6306-1), trixie in 6.12.90-1 (DSA-6295-1), and bullseye in 5.10.257-1 (DLA-4606-1).
  • Ubuntu had fixed its kernels on every supported release; only linux-azure-nvidia on 24.04 was still pending.
  • Red Hat listed every affected product as fixed, and RHEL 6 and 7 as not affected.

Live patches apply without a reboot. Canonical Livepatch covers CVE-2026-46300 (LSN-0122-1 (opens in a new tab), October 7), and Red Hat ships kpatch updates for some RHEL 8 and 9 extended-support streams. Confirm with your vendor's tooling that the patch is loaded.

Check containers and Kubernetes

Shell
# Local images and the version inside onedocker images --format '{{.Repository}}:{{.Tag}}  {{.ID}}  {{.CreatedSince}}' | grep -i phpdocker run --rm --entrypoint php <image> -v# Running containersdocker ps --format '{{.ID}}  {{.Image}}  {{.Names}}'docker exec <container> php -v# Kubernetes: every pod image, cluster-widekubectl get pods -A -o jsonpath='{range .items[*]}{.metadata.namespace}{"\t"}{.metadata.name}{"\t"}{range .spec.containers[*]}{.image}{" "}{end}{"\n"}{end}' | grep -i php

A tag encodes the SAPI: php:8.2-apache is mod_php, php:8.2-fpm is FPM. Images that bundle PHP under another name (wordpress:…, for instance) won't match a php grep; check those with php -v inside the container.

The official php Docker images were updated on October 21. When we checked around 11:10 AM CDT, Docker Hub was serving 8.2.35, 8.3.36, 8.4.27, and 8.5.12, and the moving 8.2–8.5 and latest tags resolved to them (pushed around 10:40 AM CDT). Earlier that morning, the same tags still pointed at the vulnerable 8.2.34, 8.3.35, 8.4.26, and 8.5.11 builds, so anything pulled before then needs a fresh pull. Rebuild with docker build --pull; cached layers and digest-pinned images (php:8.2@sha256:…) won't update on their own.

Check repositories and CI pipelines

Shell
# PHP base images in Dockerfiles and Containerfiles, any registry or variantgrep -rniE --exclude-dir=node_modules \  --include='Dockerfile*' --include='Containerfile*' --include='*.dockerfile' \  '^[[:space:]]*FROM[[:space:]].*php:' .# CI pipelines, compose files, and setup-php actionsgrep -rnE --exclude-dir=node_modules --include='*.yml' --include='*.yaml' --include='Dockerfile*' \  'php:[0-9]|php-version|shivammathur/setup-php' .

We tested these patterns with GNU grep 3.8 against a fixture repo: they catch --platform and registry-prefixed FROM lines and shivammathur/setup-php pins, and skip node_modules.

How to fix

Update PHP and restart every worker

Install the release for your branch — 8.5.12, 8.4.27, 8.3.36, or 8.2.35 — or your distribution's fixed package. Then restart every PHP worker: a patched binary on disk does nothing until the running FPM pools and Apache processes are replaced.

Shell
systemctl restart php8.3-fpm                  # FPM (the unit name matches your branch)systemctl restart apache2                     # mod_php on Debian/Ubuntu (httpd on RHEL)kubectl rollout restart deployment/<name>     # containers: roll the pods onto the new image

On 8.1, 8.0, or 7.4, get a backported package from your distribution or LTS vendor, or build from PHP's source backport (see end-of-life versions). Both are stopgaps; the real fix is moving to a supported branch.

Turn session upload progress off, even after patching. On October 23, PHP published an informational advisory (opens in a new tab) for a third CVE, CVE-2026-115560: "We suggest you set session.upload_progress.enabled=0 until the next regular bugfix release, to fully protect from an unlikely RCE vector." PHP says it "can only occur under an unusual combination of configuration and application code," and that "Applications that never change the serialize handler at runtime can keep the feature enabled." It will publish a full advisory with the next release. If you set it on October 21, keep it.

Patch the Linux kernel and reboot

Install your distribution's kernel update for CVE-2026-46300, then reboot. Red Hat: "The system must be rebooted for this update to take effect." Ubuntu's unattended upgrades install the fix automatically, "but a reboot is still required." Live patches are the exception. Reboot container hosts and Kubernetes nodes too; appliances need their vendor's update.

On a server that ran a vulnerable PHP, run the compromise checks before you reboot. The kernel bug's changes exist only in memory, so the reboot that applies the fix also erases them.

If you can't reboot yet, Ubuntu and Wiz publish the same interim mitigation: block the kernel modules that this bug and the related Dirty Frag bugs live in. It breaks what uses them, including IPsec VPNs such as strongSwan:

Shell
printf 'install %s /bin/false\n' esp4 esp6 rxrpc \  | sudo tee /etc/modprobe.d/dirty-frag.confsudo rmmod esp4 esp6 rxrpc 2>/dev/nullgrep -E '^(esp4|esp6|rxrpc) ' /proc/modules || echo "Not loaded"

If the last line lists a module, something is using it, and the block takes effect at the next reboot. Ubuntu says the block is no longer needed once the kernel update is installed. Wiz also suggests restricting unprivileged user namespaces where that's feasible. We checked the block's syntax with a modprobe dry run.

Check for signs of compromise

The details leaked a day before the fixes shipped, so patching isn't the end of it. The FBI's Cyber Division asks organizations to "monitor web servers for suspicious activity, including PHP processes unexpectedly launching command shells or downloading files." A starting point:

Shell
# Everything running as the web server's user: expect only php-fpm or apache2 workers# (www-data on Debian/Ubuntu; apache, nginx, or the FPM pool's user elsewhere)ps -u www-data -o pid,ppid,lstart,args# Worker crashes since the leak: failed exploit attempts tend to crash workersjournalctl _TRANSPORT=kernel --since 2026-10-20 | grep -i segfault   # across rebootsgrep -h SIGSEGV /var/log/php*-fpm.log /var/log/php-fpm/error.log 2>/dev/nullgrep -h 'Segmentation fault' /var/log/apache2/error.log   # RHEL: httpd/error_logdocker logs <container> 2>&1 | grep -E 'SIGSEGV|Segmentation fault'   # containers# PHP files created or changed under the web root since the leak (adjust the path)find /var/www -type f -name '*.php' -newermt 2026-10-20 -ls

A shell, curl, wget, or an unfamiliar binary running as the web user is a red flag, and so is a PHP file that no deploy explains.

Look for root-level changes too, before you reboot. Where PHP2Shell could reach a kernel without the CVE-2026-46300 fix, assume the attacker could get root. In Dream's report, the attacker planted a small PHP webshell in a publicly reachable directory, then built a reverse SSH tunnel "wrapped in a systemd service and an rc.local boot hook." The kernel bug's own changes live only in memory, so check system files against their packages before a reboot clears them:

Shell
# System files that don't match their packages (run before rebooting)dpkg --verify | grep -v '^missing'    # Debian/Ubuntu; "c" marks config filesrpm -Va                               # RHEL and derivatives; slow on big installs# Services and boot hooks created or changed since the leakfind /etc/systemd /etc/rc.local /lib/systemd/system /usr/lib/systemd/system \  -newermt 2026-10-20 ! -type d -ls 2>/dev/null# SSH client processes: sshd is the server, an outbound ssh is unusual herepgrep -ax ssh

Your own config edits and recent package updates will show up. What matters is a change nothing explains, especially to su, sudo, or anything under /etc/pam.d/. Package verification reads files the way every other program does, through the page cache, so it should see a change the kernel bug made in memory. We tested these in Debian 12 and Rocky Linux 9 containers against a changed /etc/pam.d/su and su binary written to disk, not against the exploit itself.

A clean result isn't proof of safety. If you find signs of compromise, the FBI asks you to "isolate affected systems, preserve your web server and PHP logs," and report it to your local FBI field office or IC3 (opens in a new tab).

Rotate secrets even if the checks come back clean. CVE-2026-109619's memory disclosure doesn't start a shell or write a file, so nothing above would show it. For internet-facing servers that ran a vulnerable version, change the credentials their PHP processes held: database passwords, API keys, and session and signing secrets.

If you can't patch immediately

Take the system offline until you can patch it. The FBI's Cyber Division says (opens in a new tab): "If an immediate update is not feasible it is recommended that organizations take the system offline until it can be fully mitigated." CERT-EU (opens in a new tab) advises "isolating internet-facing applications from public networks until a fix is applied and verified." CISA (opens in a new tab) says organizations that can't update right away, or that run PHP 8.1 or earlier, "should take PHP-based systems offline until they can be patched or updated." It's disruptive, but it's a smaller incident than an attacker running code on your server.

If the system has to stay online, apply PHP's interim measures administratively — in php.ini, the FPM pool, or the server configuration, not ini_set() or .user.ini — and restart every worker.

For CVE-2026-109618 (out-of-memory corruption):

  • Set memory_limit=-1 administratively, and make sure nothing — pool, directory, or app — puts a finite limit back. This removes the controllable trigger, but an underlying allocation failure can still reach the bug. It also lets one request take as much memory as it can get, so pair it with the container or cgroup limit below.
  • Set a conservative post_max_size (8M if you don't accept uploads, 32M if you do), keep upload_max_filesize below it, and enforce request-size, field-count, part-count, header-count, and nesting limits at the proxy — including for requests with no usable Content-Length. If you don't use multipart forms, block them at the frontend.
  • Use a container or cgroup memory limit as an availability boundary, ideally one that kills only the affected worker. Do not use RLIMIT_AS or RLIMIT_DATA: they cause the exact allocation failure that triggers the bug.

For CVE-2026-109619 (stale global state):

  • Set session.upload_progress.enabled=0 and restart every worker. This blocks the confirmed session paths, not other variants. PHP now suggests keeping it off after patching too, until its next regular release (CVE-2026-115560).
  • On PHP 8.5, set fatal_error_backtraces=0 and restart every worker. This blocks the confirmed fatal-backtrace path only.
  • Remove invalid or deprecated per-request INI settings that emit diagnostics before initialization. Hiding diagnostics with error_reporting, display_errors, or @ does not help. Fix attacker-reachable fatal errors and execution timeouts. If you can absorb the cost, pm.max_requests=1 recycles each FPM worker after a single request, which means starting a new process for every request.

End-of-life versions

PHP 8.1, 8.0, and 7.4 get no official release. Instead, "given the severity of these vulnerabilities," PHP's security team published minimal source-only backports for those three branches: single commits by Arnaud Le Blanc, dated October 18, on branches named for the CVEs. "Minimal" is literal. On the supported branches, the fix adds about 11,000 lines across roughly 400 files, nearly two-thirds of them tests; the backports add 230 to 310 lines across 17 to 23 files.

Avoid state corruption via bailout
php/php-src · Arnaud Le Blanc · Oct 18, 2026
8.5.1231c0ea7
423 files
11,556 lines added, 1,017 removed
8.4.27506e87f
402 files
11,112 lines added, 1,032 removed
8.3.363c832b5
392 files
10,833 lines added, 1,020 removed
8.2.3501a40e8
389 files
10,759 lines added, 988 removed
8.1 backport1d7dec1
23 files · branch PHP-8.1-CVE-2026-109618-109619
311 lines added, 73 removed
8.0 backport82f8f31
17 files · branch PHP-8.0-CVE-2026-109618-109619
229 lines added, 59 removed
7.4 backport712e60f
17 files · branch PHP-7.4-CVE-2026-109618-109619
240 lines added, 59 removed

The backports are unofficial, with no binaries and no ongoing support. Installing php8.1 from an old repository or pulling an old php:8.1-apache tag gets you none of it unless your vendor ships the fix. For 7.3 and older, PHP offers nothing.

PHP 8.2 reaches end-of-life on December 31, 2026. Patch to 8.2.35 now, then plan the move to 8.4 or 8.5, so you're not back here at year's end with no release to take.

Timeline and exploitation status

All times are CDT (UTC−5).

  • Fix
  • Advisory or rating
  • Exploit or proof of concept
  1. Oct 30
    1. Cisco reports a fix deployed for ISE Portal Builder and names 26.2.1.9 as the fix for Ultra-Reliable Wireless Backhaul

  2. Oct 29
    1. Dream's updated report names the rooted firewalls as Palo Alto Networks PAN-OS, and Unit 42 says it has confirmed the reported results

    2. Palo Alto's advisory reports "Active exploitation" against management interfaces exposed to the internet

    3. Palo Alto lists hotfixes as released for every supported PAN-OS branch

  3. Oct 28
    1. 2:00 PMCISA adds (opens in a new tab) CVE-2026-46300 to KEV, citing the chain with PHP2Shell; federal civilian agencies must remediate by October 31

  4. Oct 27
    1. By 12:10 PMPalo Alto reports "very limited exploitation" of the PAN-OS management interface

    2. 11:40 AMPalo Alto Networks raises its advisory to Critical

  5. Oct 26
    1. Dream publishes its report

    2. CISA adds (opens in a new tab) both CVEs to its KEV catalog; under BOD 26-04, federal civilian agencies must remediate by October 29 and run a forensic triage

  6. Oct 23–24
    1. Per Dream, a campaign chaining PHP2Shell with Fragnesia roots 24 firewalls and one internal firewall management server in the US, Japan, Taiwan, and South Korea

  7. Oct 23
    1. PHP's informational advisory for CVE-2026-115560 suggests keeping session upload progress off until the next regular release

  8. Oct 22
    1. 7:58 AMRemi's repository publishes fixed RPMs

  9. Oct 21
    1. CISA publishes an alert, "Critical Vulnerabilities in PHP Require Immediate Patching (opens in a new tab)"

    2. CERT-EU publishes Security Advisory 2026-018

    3. ~10:40 AMUpdated official php images pushed to Docker Hub

    4. 9:59 AMThe FBI's Cyber Division posts a critical vulnerability alert: "Patch and Hunt Immediately"

    5. 8:48–8:54 AMBoth CVE records published

    6. 8:30 AMPHP releases 8.5.12, 8.4.27, 8.3.36, and 8.2.35, half an hour early

    7. 3:31 AMThe earliest public GitHub repository we found presenting itself as a proof of concept is created

  10. Oct 20
    1. PHP pre-announces (opens in a new tab) a critical security release for October 21 at 9:00 AM CDT

    2. 1:26 PMwatchTowr confirms (opens in a new tab) the leaked vulnerabilities are real; disclosure had been embargoed until Thursday, October 22

    3. 11:39 AMKevin Beaumont reports (opens in a new tab) that the two CVEs have leaked before the patch

  11. May 23
    1. Stable kernels 5.10.257, 5.15.208, 6.1.174, 6.6.141, 6.12.91, 6.18.33, and 7.0.10 ship the fix, and its CVE record is published

  12. May 13
    1. Fragnesia (CVE-2026-46300), a Linux kernel privilege escalation, is disclosed (opens in a new tab) with a fix and a public proof of concept

Exploitation. CERT-EU reports proofs of concept circulating, which "raises the likelihood that attackers are already exploiting the vulnerabilities." watchTowr's FAQ (opens in a new tab) says its honeypot network has observed exploitation in the wild since October 21, and Cloudflare's CTO, Dane Knecht, said the company was "seeing early attacks emerging," per Tenable (opens in a new tab). CISA added (opens in a new tab) both CVEs to its KEV catalog (opens in a new tab) on October 26, after urging organizations on October 21 to "immediately patch" them. Under BOD 26-04 (opens in a new tab), federal civilian executive branch agencies must remediate by October 29 and "carry out a forensic triage of the asset to assess whether the system is compromised." The directive "applies only to FCEB agencies," but CISA encourages every organization to prioritize KEV fixes.

On October 28, CISA added the Linux kernel's CVE-2026-46300 to the catalog for its chain with these bugs, due October 31 with the same forensic triage. Dream (opens in a new tab) reports recovering artifacts of a campaign that used that chain to root 25 servers in the United States, Japan, Taiwan, and South Korea, "including systems in a US government-affiliated environment": 24 Palo Alto Networks PAN-OS firewalls and one internal firewall management server, from which the attacker went after Active Directory. Palo Alto's Unit 42 (opens in a new tab) says it "independently verified the same attacker's tooling and confirmed the reported results." Dream says "multiple indicators point to a Chinese-nexus operation," but "We do not attribute this activity to a named threat actor." CISA's catalog entry doesn't mention the campaign or a count. Separately, Palo Alto Networks (opens in a new tab) reports "Active exploitation has been observed targeting the Palo Alto Networks management interface exposed to the internet."

The catalog lists known ransomware use as "Unknown" for all three CVEs (as of 11:05 PM CST, November 3). We haven't tested any public proof of concept, and we aren't linking them.

Updates to this post

We'll revise this post and mark it updated as the picture changes: a Red Hat fix for RHEL 9's php:8.4 stream, PHP's full advisory and fix for CVE-2026-115560, appliance vendors' fixes, and confirmed compromises.

  1. Latest

    Dream's report, updated October 29, names the rooted firewalls as Palo Alto Networks PAN-OS on the 12.1 and 12.2 branches, and Palo Alto's Unit 42 says it confirmed the reported results. Corrected: we had said Dream didn't name the vendor. Cisco has deployed a fix for ISE Portal Builder, which we had listed as taken offline, and names 26.2.1.9 as the fix for Ultra-Reliable Wireless Backhaul, still expected in November. Palo Alto says CVE-2026-115560 doesn't affect PAN-OS. Debian's testing release now has the fixed 8.4.27-1. Added that PHP 8.6.0 RC4 carries the fixes. Unchanged: the KEV entries, Red Hat's affected RHEL 9 php:8.4 stream, the missing fix for CVE-2026-115560, Fortinet's investigation, and the kernel fixes for CVE-2026-46300.

Show 2 earlier updates
  1. Added the Linux kernel's CVE-2026-46300 ("Fragnesia"), which CISA added to KEV on October 28 for its chain with these bugs, along with Dream's report and Palo Alto Networks' exploitation status. New sections cover the chain, checking and patching the kernel, and root-level compromise checks; appliance vendors' status is under Who is affected. Added PHP's October 23 advisory for CVE-2026-115560, which our October 26 update missed. Corrected: NVD scores CVE-2026-109619 8.1, not 9.8 (since October 22); the weakness row lacked CWE-1419; Remi's repository has had fixed RPMs since October 22; Red Hat now lists RHEL 6's PHP as affected by both CVEs, and has fixed RHEL 7's for ELS subscribers.

  2. CISA added both CVEs to its KEV catalog, with an October 29 remediation deadline and a forensic-triage requirement for federal civilian agencies under BOD 26-04. Added CISA's October 21 alert to the timeline, and its guidance to take unpatched systems offline to If you can't patch immediately. Updated the distribution status: Debian has fixed unstable, and Red Hat has fixed RHEL 8's php:8.2 stream; RHEL 9's php:8.4 stream is still affected.

Get help

For an outside view, our free security audit checks the domains and public IPs you verify for what an attacker can see: exposed services, publicly visible software versions with known CVEs, TLS, email security, DNS, and HTTP headers.

Atlas Service
Free Security Audit
Non-destructive checks of your verified domains and public IPs, and a PDF report with every finding ranked and a fix for each, within 3 business days of verification.

This is the second of two critical runtime disclosures we're covering from October 21. The other: a remote-code-execution bug in Google's Brotli decoder, patched first in Node.js, with the same container-inventory problem underneath. PHP's Windows builds picked up that fix on October 26, as 8.5.12-1, 8.4.27-1, 8.3.36-1, and 8.2.35-1.

Sources

PHP

Advisories

Appliance vendors

CVE records

Distributions

Linux kernel

Containers

Research and reporting

Atlas Security
Security Advisories

The Atlas security byline: write-ups of vulnerabilities in widely deployed software — what changed, who is exposed, and what to check — verified against primary sources.

Continue reading

More from the Atlas Meridian

Security
13 min read

APT's November 2026 Download Verification Bypass: CVE-2026-109518

An APT flaw lets an on-path attacker swap a verified package and run code as root on Debian, Ubuntu, and derivatives. Debian and Ubuntu have fixes out.

Atlas Security
Security Advisories
View category
Security
29 min read

Google Brotli's October 2026 Decoder RCE: CVE-2026-111497

CVE-2026-111497 (Node2Shell) is a CVSS 9.2 RCE in Google's Brotli decoder, now in CISA's KEV. Fixed in Brotli 1.2.1 and Node.js 22.23.4, 24.22.1, and 26.12.1.

Atlas Security
Security Advisories
View category
Security
11 min read

OpenSSH's November 2026 Password Authentication Bypass on musl: 10.6p2

OpenSSH 10.6p2 fixes a critical password-auth bypass that lets a remote attacker log in to musl systems without PAM, such as Alpine. No CVE. Who's exposed and what to do.

Atlas Security
Security Advisories
View category
Engage · Atlas Engineering

Reading is one thing. Shipping is another.

If this writeup resonates with what you're building, let's talk. We'll connect you directly with an engineer to assist.