Securitysshole: password bypass in Alpine’s OpenSSH

PHP2Shell (CVE-2026-109618, CVE-2026-109619): patch status by vendor

Two unauthenticated remote code execution flaws in the PHP runtime itself, not in any one application. Fixed upstream in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

Exploited in the wild: CISA added both CVEs to its Known Exploited Vulnerabilities catalog on Oct 26, 2026, with a federal remediation deadline of Oct 29. Cloudflare had reported early attack attempts (via BleepingComputer).

What to do now

  1. Update every PHP installation that serves web requests (PHP-FPM, Apache mod_php, php-cgi, FrankenPHP, LiteSpeed) to 8.5.12, 8.4.27, 8.3.36 or 8.2.35 — or to your vendor's fixed build.
  2. Restart PHP-FPM, Apache and long-running workers so they load the patched binary, then verify the binary that serves traffic (php-fpm -v), not only the CLI.
  3. Rebuild container images from a freshly pulled php base image; images built before Oct 21 still contain the vulnerable version.
  4. On PHP 8.1 or older there is no official release: use a vendor backport, apply the interim mitigations below and plan an upgrade.

Fixed PHP versions

The CVE records and GitHub advisories list PHP 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27 and 8.5 before 8.5.12. The PHP team's source backports for 7.4, 8.0 and 8.1 imply those branches are affected too; Wiz, one of the reporters, says versions back to 5.4 are affected. No official source names the earliest affected version.

Am I patched?

Run one of these on your server or container and paste the output. Nothing leaves this page.

  • php -v:php -v
  • PHP-FPM:php-fpm8.3 -v # or php-fpm -v
  • Debian / Ubuntu:dpkg -l 'php*' | grep ^ii
  • Alpine:apk info -v | grep ^php
  • RHEL / Alma / Rocky / Amazon:rpm -qa 'php*'
  • Docker:docker run --rm <your-image> php -v
Versions only — we never scan or contact your servers.

Who has shipped the fix

Distributions and hosting panels often backport the fix without changing the PHP version number, so compare your package version with the vendor’s fixed build — not with php.net.

PHP (php.net source releases)

8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix both CVEs; no newer release as of Oct 27. 7.4, 8.0 and 8.1 only have unreleased minimal source backports on php-src branches.

  • 8.5: php 8.5.12
  • 8.4: php 8.4.27
  • 8.3: php 8.3.36
  • 8.2: php 8.2.35

Check: php-fpm -v # or php -v; also check the SAPI that serves traffic

PHP for Windows (windows.php.net)

Official TS/NTS builds of 8.5.12, 8.4.27, 8.3.36 and 8.2.35 were published on Oct 21. The newest 8.1, 8.0 and 7.4 Windows builds predate the fix.

  • 8.5: php (Win32 vs17) 8.5.12
  • 8.4: php (Win32 vs17) 8.4.27
  • 8.3: php (Win32 vs16) 8.3.36
  • 8.2: php (Win32 vs16) 8.2.35

Check: php -v # for IIS FastCGI also run php-cgi.exe -v

Docker official php images

All supported tags (8.2–8.5, latest; cli, apache, fpm, zts; Debian and Alpine) were rebuilt on Oct 21–22. The 8.1, 8.0 and 7.4 tags are end-of-life, are no longer rebuilt and stay vulnerable.

  • php:8.5 / latest: library/php 8.5.12
  • php:8.4: library/php 8.4.27
  • php:8.3: library/php 8.3.36
  • php:8.2: library/php 8.2.35

Check: docker pull php:8.4-fpm && docker run --rm php:8.4-fpm php -v # then rebuild images FROM it

Debian

trixie (DSA-6574-1), bookworm LTS (DLA-4848-1), forky and sid are fixed; 8.4.27-1 migrated to forky on Oct 24. bullseye and older get fixes only through Freexian's paid ELTS.

  • trixie (13): php8.4 8.4.27-1~deb13u1
  • bookworm (12, LTS): php8.2 8.2.35-1~deb12u1
  • forky (testing), sid: php8.4 8.4.27-1

Check: dpkg -l 'php*' | grep ^ii

Ubuntu

Rated Critical. Fixed in 26.10, 26.04 LTS, 24.04 LTS and 22.04 LTS (USN-8948-1); 20.04 and older through Ubuntu Pro (USN-8948-2). The version keeps the old upstream number.

  • 26.10: php8.5 8.5.9-0ubuntu2.1
  • 26.04 LTS: php8.5 8.5.4-0ubuntu1.5
  • 24.04 LTS: php8.3 8.3.6-0ubuntu0.24.04.13
  • 22.04 LTS: php8.1 8.1.2-1ubuntu2.28
  • 20.04 LTS (Pro): php7.4 7.4.3-4ubuntu2.29+esm5
  • 18.04 LTS (Pro): php7.2 7.2.24-0ubuntu0.18.04.17+esm14

Check: dpkg -l 'php*' | grep ^ii # on Pro systems: pro fix CVE-2026-109618

Red Hat Enterprise Linux

Errata shipped for RHEL 10, RHEL 9 (php 8.0, php:8.2, php:8.3), RHEL 8 (php:7.4, php:8.2) and, by Oct 26, the extended-support minor releases (EUS, E4S, AUS, TUS). RHEL 7 ELS got a fix for CVE-2026-109619 only (Red Hat lists RHEL 7 as not affected by CVE-2026-109618). The RHEL 9 php:8.4 module stream is still affected with no fix. Red Hat rates the CVEs Important (CVSS 3.1 8.1).

  • RHEL 10 (RHSA-2026:87070): php 8.3.36-1.el10_2
  • RHEL 10 (RHSA-2026:87071): php8.4 8.4.27-1.el10_2
  • RHEL 9 (RHSA-2026:87151): php 8.0.30-8.el9_8.1
  • RHEL 9 php:8.2: php 8.2.35-1.module+el9.8.0+25111+a1450321
  • RHEL 9 php:8.3: php 8.3.36-1.module+el9.8.0+25109+6886e21a
  • RHEL 8 php:7.4: php 7.4.33-8.module+el8.10.0+25117+30337cca
  • RHEL 8 php:8.2 (RHSA-2026:87073): php 8.2.35-1.module+el8.10.0+25110+f67151d2
  • RHEL 10.0 E2S (RHSA-2026:88561): php 8.3.19-1.el10_0.2
  • RHEL 9.6 EUS (RHSA-2026:88720): php 8.0.30-3.el9_6.2
  • RHEL 9.6 EUS php:8.2 (RHSA-2026:88834): php 8.2.28-1.module+el9.6.0+25176+d8415d54.4
  • RHEL 9.6 EUS php:8.3 (RHSA-2026:89111): php 8.3.19-1.module+el9.6.0+25160+f8b750a4.3
  • RHEL 9.4 E4S (RHSA-2026:88725): php 8.0.30-1.el9_4.2
  • RHEL 9.4 E4S php:8.2 (RHSA-2026:88835): php 8.2.13-1.module+el9.4.0+25177+88c847cf.4
  • RHEL 9.2 E4S (RHSA-2026:88659): php 8.0.30-1.el9_2.2
  • RHEL 8.8 TUS/E4S php:7.4 (RHSA-2026:88532): php 7.4.33-1.module+el8.8.0+25148+55cf9df9.2
  • RHEL 8.6 EUS extension php:7.4 (RHSA-2026:88533): php 7.4.19-4.module+el8.6.0+25157+c2ff122e.3
  • RHEL 8.4 AUS php:7.4 (RHSA-2026:88565): php 7.4.6-5.module+el8.4.0+25156+e0c98721.3
  • RHEL 7 ELS, CVE-2026-109619 only (RHSA-2026:88693): php 5.4.16-48.el7_9.1

Check: rpm -qa 'php*' ; dnf updateinfo list --cve CVE-2026-109618

AlmaLinux

AlmaLinux shipped its own patched builds for its PHP streams on 8, 9 and 10 (including retired ones) with an '.alma.1' suffix that keeps the old upstream version; the Red Hat rebuilds are available too. Rows below list the builds we verified.

  • AlmaLinux 10: php 8.3.33-1.el10_2.alma.1
  • AlmaLinux 10: php8.4 8.4.24-1.el10_2.alma.1
  • AlmaLinux 9: php 8.0.30-8.el9_8.alma.1
  • AlmaLinux 9 php:8.1: php 8.1.32-1.module_el9.8.0+326+528679fc.alma.1
  • AlmaLinux 9 php:8.2: php 8.2.33-1.module_el9.8.0+327+37dfd4b4.alma.1
  • AlmaLinux 9 php:8.3: php 8.3.33-1.module_el9.8.0+328+1fdeb728.alma.1
  • AlmaLinux 8 php:8.0: php 8.0.30-1.module_el8.10.0+4319+26f10322.alma.1
  • AlmaLinux 8 php:8.2: php 8.2.33-1.module_el8.10.0+4320+c30d6dbb.alma.1

Check: rpm -q php-common # compare the full version-release; php -v cannot show the backport

Rocky Linux

Rocky rebuilt seven Red Hat errata on Oct 22 (Rocky 10, Rocky 9 php 8.0/8.2/8.3, Rocky 8 php:7.4 and php:8.2). The EL9 php:8.4 stream is still unfixed because Red Hat has no fix for it yet.

  • Rocky 10 (RLSA-2026:87070): php 8.3.36-1.el10_2
  • Rocky 10 (RLSA-2026:87071): php8.4 8.4.27-1.el10_2
  • Rocky 9 (RLSA-2026:87151): php 8.0.30-8.el9_8.1
  • Rocky 9 php:8.2 (RLSA-2026:87072): php 8.2.35-1.module+el9.8.0+40395+2f706e64
  • Rocky 9 php:8.3 (RLSA-2026:87079): php 8.3.36-1.module+el9.8.0+40396+4e680bb7
  • Rocky 8 php:7.4 (RLSA-2026:87080): php 7.4.33-8.module+el8.10.0+40393+c071e357
  • Rocky 8 php:8.2 (RLSA-2026:87073): php 8.2.35-1.module+el8.10.0+40394+d21b33fb

Check: rpm -qa 'php*' ; dnf updateinfo list --cve CVE-2026-109618

CentOS Stream

No advisories. Stream 10 serves php 8.3.36-1.el10; Stream 9 serves php 8.0.30-9.el9 and, since Oct 23, fixed php:8.2, php:8.3 and php:8.4 module builds. The Stream 10 php8.4 fix (8.4.27-2.el10) is built but not on the mirror yet; the retired Stream 9 php:8.1 module gets no fix.

  • Stream 10: php 8.3.36-1.el10
  • Stream 9: php 8.0.30-9.el9
  • Stream 9 php:8.2: php 8.2.35-1.module_el9+1447+c2e1e9ab
  • Stream 9 php:8.3: php 8.3.36-1.module_el9+1448+8542a8fd
  • Stream 9 php:8.4: php 8.4.27-1.module_el9+1449+ae7b4724

Check: rpm -qa 'php*'

Fedora

Both current releases are fixed: Fedora 44 (php 8.5.12, stable Oct 21) and Fedora 43 (php 8.4.27, stable Oct 22).

  • Fedora 44: php 8.5.12-1.fc44
  • Fedora 43: php 8.4.27-2.fc43

Check: rpm -q php-cli

Amazon Linux

Amazon Linux 2023 fixed php8.2–8.5 (ALAS2023-2026-3301…3304) and AL2's PHP 8.2 extras topic. AL2023 php8.1 and AL2 core php are 'No Fix Planned'.

  • AL2023: php8.2 8.2.35-1.amzn2023.0.1
  • AL2023: php8.3 8.3.36-1.amzn2023.0.1
  • AL2023: php8.4 8.4.27-1.amzn2023.0.1
  • AL2023: php8.5 8.5.12-1.amzn2023.0.1
  • AL2 php8.2 extras: php 8.2.35-1.amzn2.0.1

Check: rpm -qa 'php*'

SUSE / openSUSE

Fixed for SLES 16.0 and openSUSE Leap 16.0, SLES 15 SP7 and the SP4–SP6 LTSS lines (php8 and php7), SLES 12 SP5 LTSS (php74) and Tumbleweed. SLES 16.1/16.2 and openSUSE Leap 16.1 (php8 8.5.8) are still listed as affected.

  • SLES 16.0, openSUSE Leap 16.0 (SUSE-SU-2026:24271-1): php8 8.4.27-160000.1.1
  • SLES 15 SP7: php8 8.3.36-150700.3.24.1
  • SLES 15 SP6 LTSS (SUSE-SU-2026:4843-1): php8 8.2.35-150600.3.39.1
  • SLES 15 SP4/SP5 LTSS (SUSE-SU-2026:4852-1): php8 8.0.30-150400.4.80.1
  • SLES 15 SP4–SP7 (SUSE-SU-2026:4853-1): php7 7.4.33-150400.4.81.1
  • SLES 12 SP5 LTSS (SUSE-SU-2026:4870-1): php74 7.4.33-1.74.1
  • openSUSE Tumbleweed: php8 8.5.12-1.1

Check: rpm -q php8 ; zypper lp --cve=CVE-2026-109618

Alpine Linux

Every PHP package on edge and v3.21–v3.24 has a fixed build (Oct 21–22). Community-repo support has ended for v3.21–v3.23, so future PHP fixes there are not guaranteed.

  • edge, v3.21–v3.24: php83 8.3.36-r0
  • edge, v3.21–v3.24: php84 8.4.27-r0
  • edge, v3.23, v3.24: php85 8.5.12-r0
  • v3.21, v3.22: php82 8.2.35-r0

Check: apk info -v | grep ^php

Ondřej Surý (ppa:ondrej/php, packages.sury.org)

Rebuilt packages on Oct 21: 8.2–8.5 carry the fixed upstream releases; the backport is verified in the 7.0, 7.4, 8.0 and 8.1 builds (their changelogs name both CVEs). Builds of 7.1–7.3 were not verified.

  • Ubuntu 24.04 PPA: php8.1 8.1.34-9+ubuntu24.04.1+deb.sury.org+1
  • Ubuntu 24.04 PPA: php7.4 1:7.4.33-31+ubuntu24.04.1+deb.sury.org+1
  • Ubuntu 22.04 PPA: php8.1 8.1.34-9+ubuntu22.04.1+deb.sury.org+1
  • Ubuntu 22.04 PPA: php7.4 1:7.4.33-31+ubuntu22.04.1+deb.sury.org+1
  • Debian 13 (packages.sury.org): php8.1 8.1.34-9+0~20261021.82+debian13~1.gbp4e430a
  • Debian 12 (packages.sury.org): php8.1 8.1.34-9+0~20261021.82+debian12~1.gbp4e430a
  • Debian 12 (packages.sury.org): php7.4 1:7.4.33-31+0~20261021.121+debian12~1.gbpe9c428

Check: apt-cache policy php8.3-cli # substitute your branch

Remi's RPM repository

EL 8/9/10 modules and SCLs carry 8.2.35, 8.3.36, 8.4.27 and 8.5.12 plus backports for 7.4, 8.0 and 8.1. On Oct 27 EL 8 got backports for 7.2 and 7.3 (the Oct 25 builds 7.2.34-30 and 7.3.33-23 lacked the proper patch). The 5.6–7.1 builds do not mention these CVEs; the EL 7 repository is frozen.

  • EL 9 php:8.1: php 8.1.34-6.module_php.8.1.el9.remi
  • EL 9 php:8.0: php 8.0.30-21.module_php.8.0.el9.remi
  • EL 9 php:7.4: php 7.4.33-31.module_php.7.4.el9.remi
  • EL 8 php:8.1: php 8.1.34-6.module_php.8.1.el8.remi
  • EL 8 php:7.4: php 7.4.33-31.module_php.7.4.el8.remi
  • EL 9 SCL: php81-php 8.1.34-6.el9.remi
  • EL 9 SCL: php74-php 7.4.33-31.el9.remi
  • EL 8 php:remi-7.3: php 7.3.33-24.module_php.7.3.el8.remi
  • EL 8 php:remi-7.2: php 7.2.34-31.module_php.7.2.el8.remi
  • EL 8 SCL: php73-php 7.3.33-24.el8.remi
  • EL 8 SCL: php72-php 7.2.34-31.el8.remi

Check: rpm -qa 'php*' ; dnf module list --enabled php

Plesk

Fixed builds for every PHP Plesk ships and for sw-engine. EOL 7.4/8.0/8.1 were rebuilt under the same version numbers: the build date must be Oct 21, 2026 or later. Plesk itself must be on 18.0.80 Update 11 or 18.0.81 Update 4.

  • PHP 8.5: plesk-php85 8.5.12
  • PHP 8.4: plesk-php84 8.4.27
  • PHP 8.3: plesk-php83 8.3.36
  • PHP 8.2: plesk-php82 8.2.35
  • PHP 8.1 (EOL rebuild, built Oct 21 2026 or later): plesk-php81 8.1.34
  • PHP 8.0 (EOL rebuild, built Oct 21 2026 or later): plesk-php80 8.0.30
  • PHP 7.4 (EOL rebuild, built Oct 21 2026 or later): plesk-php74 7.4.33

Check: /opt/plesk/php/8.1/bin/php -v # build date must be Oct 21 2026 or later

cPanel & WHM (EasyApache 4)

EasyApache 4 25.91 moves ea-php82–85 to the fixed releases and backports the fix into ea-php74/80/81 without changing their versions; cPanel & WHM 136.0.50 updates cpanel-php84. Restart Apache/PHP-FPM after updating.

  • EA4 25.91: ea-php85 8.5.12
  • EA4 25.91: ea-php84 8.4.27
  • EA4 25.91: ea-php83 8.3.36
  • EA4 25.91: ea-php82 8.2.35

Check: rpm -q ea-php82 ea-php83 ea-php84 ea-php85 ; /usr/local/cpanel/cpanel -V

CloudLinux (alt-php, ea-php)

ea-php52–85 is fixed on CL7–CL10 and alt-php 5.2–8.5 on CL7/8/9 (Oct 22, backported under lower version numbers); CL10 alt-php comes from the ELS repository. Native PHP packages reached stable on Oct 22. alt-php on CloudLinux 6 is not confirmed and the status incident is still open. Run a full (not --security) update of 'alt-php*' and 'ea-php*'.

Check: rpm -q --changelog alt-php82-common | grep -E 'CVE-2026-(109618|109619)'

DirectAdmin (CustomBuild)

A new build moves CustomBuild PHP 8.2–8.5 to the fixed releases and patches 5.6–8.1 with unchanged versions, including the legacy RHEL 7 / Debian 10 channels (staff posts, Oct 21–22). Run 'da update' then 'da build php'.

  • CustomBuild: php8.5 8.5.12
  • CustomBuild: php8.4 8.4.27
  • CustomBuild: php8.3 8.3.36
  • CustomBuild: php8.2 8.2.35

Check: da update && da build php ; php -v

ISPConfig

The fix is your distribution's or sury.org's PHP packages plus a restart of every PHP-FPM service. ISPConfig offers a temporary 'ispconfig-multipart-guard' that blocks multipart requests (uploads break while active).

Check: php -v ; ispconfig-multipart-guard status

Webmin / Virtualmin

Virtualmin does not ship PHP: install your OS's (or PHP repository's) patched packages and restart PHP.

Check: dpkg -l 'php*' or rpm -qa 'php*'

AWS Elastic Beanstalk (PHP)

AL2023 PHP platform 4.13.13 ships 8.5.12/8.4.27 (Oct 21) and 8.3.36/8.2.35 (Oct 22). 4.13.12 was only a partial mitigation. Without managed platform updates, update the platform version manually.

  • AL2023 platform: 64bit Amazon Linux 2023 running PHP 8.x v4.13.13

Check: Environment > Platform must be 'v4.13.13 running PHP 8.x'

AWS Lambda via Bref

Patched Bref 3 and Bref 2 layers and Docker images were published Oct 21. Run 'composer update bref/bref -W' (3.0.14 or 2.4.22) and redeploy. Bref 1 and PHP 8.1 or older are not rebuilt.

  • Bref 3: bref/bref 3.0.14
  • Bref 2: bref/bref 2.4.22

Check: aws lambda get-function-configuration --function-name <fn> --query Layers

Azure App Service (PHP on Linux)

Built-in Linux PHP images with the fixed releases are on the Latest and Standard channels (Oct 21); there is no completion statement for the Extended channel yet. Built-in Windows PHP runtimes are end-of-life and get no patch: Microsoft recommends Linux or your own runtime. Custom containers must be rebuilt by the customer.

  • Latest / Standard channels: PHP 8.5 8.5.12
  • Latest / Standard channels: PHP 8.4 8.4.27
  • Latest / Standard channels: PHP 8.3 8.3.36
  • Latest / Standard channels: PHP 8.2 8.2.35

Check: Kudu WebSSH: php --version

Google App Engine (PHP)

Standard PHP 8.2+ runtimes are patched automatically. PHP 8.1 or older is not patched; App Engine flexible and custom runtimes must be redeployed on a patched PHP.

Check: Confirm the configured runtime is PHP 8.2+; redeploy flexible apps

Google Cloud Run / Cloud Run functions

PHP 8.2+ services are patched automatically only with automatic base image updates enabled; otherwise rebuild with a patched PHP and redeploy.

Check: docker run --rm YOUR_IMAGE php -v

Heroku PHP buildpack

Buildpack v298 adds 8.2.35, 8.3.36, 8.4.27 and 8.5.12 and rebuilds 8.1.34 on Heroku-22 with the EOL backport. Redeploy your apps to pick them up.

  • heroku-buildpack-php: buildpack v298

Check: heroku run php -v # 8.1.34 needs a redeploy on or after Oct 21

Laravel Cloud

Every running app was patched in place to 8.5.12/8.4.27/8.3.36/8.2.35; no action required.

Check: Optional: php -v from an app command

Laravel Vapor

Patched native PHP 8.2+ runtimes are live: redeploy. Docker-image runtimes need a new deployment. PHP 8.0/8.1 have no patch.

Check: Redeploy, then php -v in a Vapor command

Platform.sh / Upsun

Patched PHP 8.2–8.5 images on all regions by Oct 21, Dedicated clusters by Oct 22, then 7.4 and (Oct 23) 7.2–7.3; the incident closed on Oct 25. No action required; 7.1 and older are not patched.

Check: php -v in the app container

Laravel Forge

Automatic security updates do not patch PHP: click 'Update PHP X.X' for every installed version (or follow the SSH guide), then restart queue workers, Horizon and Octane. The KB lists the patched Sury package revisions down to PHP 5.6 (e.g. 8.1.34-9, 1:8.0.30-25); Ubuntu 20.04 servers should be replaced.

Check: php8.4 -v && php-fpm8.4 -v # for each installed version

Pantheon

Live, LTS and paid pre-production environments were patched on Oct 21 and the incident closed on Oct 22. Free and sandbox environments were promised within 24–48 hours; no completion update found. No action required.

Check: No action required

Kinsta

Patched PHP 7.4–8.5 across the platform; incident resolved Oct 22 08:26 UTC. No action required.

Check: WordPress Tools > Site Health > Info > Server

WP Engine

Finished deploying patched PHP to all sites on Oct 22 (7.4.33.17, 8.2.35, 8.4.27, 8.5.12). No action required.

Check: WordPress Tools > Site Health > Info > Server

Cloudways (DigitalOcean)

Autonomous was patched by Oct 22 and every active Flexible server by Oct 22 10:11 UTC (PHP 5.6 and 7.4–8.4); the incident closed on Oct 23. Support contacted a small subset of customers whose servers needed extra help. No action required.

Check: status.cloudways.com

Hostinger

All shared, cloud and cPanel hosting servers have patched PHP 5.2–8.5. VPS customers manage PHP themselves and must update and restart it.

Check: hPanel > PHP Configuration ; on VPS: php -v

GoDaddy

Managed WordPress (Oct 21), Windows Hosting and Web Hosting (cPanel, Oct 22) are patched; version numbers may not change, so check the build date. VPS customers must update PHP themselves; Web Hosting Plus and Dedicated are not mentioned.

Check: WordPress Tools > Site Health > Info > Server

SiteGround

SiteGround says it applied the official fixes across all servers on Oct 21, and staff confirmed patches for all supported PHP versions. For PHP 7.3 and 7.4, staff replies cite only server-level mitigations.

Check: Site Tools > PHP version

WordPress core

No WordPress release is needed: update PHP. Self-hosted sites on PHP older than 8.2 should consider going offline while upgrading.

Check: Tools > Site Health > Info > Server

Drupal

PSA-2026-10-20: no core release is involved; updating PHP is the only complete mitigation.

Check: Reports > Status report

Nextcloud

Operators must move to fixed PHP; Nextcloud All-in-One v14.4.1 ships it.

  • All-in-One: nextcloud-aio v14.4.1

Check: docker exec -it nextcloud-aio-nextcloud php -v

Magento / Adobe Commerce

No Adobe Commerce statement found yet (Adobe has said only that AEM and Dynamic Media are not affected). Independent researchers confirmed the issue is reachable on Magento: update PHP on every web node.

Check: php -v on every web node

Cloudflare WAF

Managed rules (including the Free Managed Ruleset) block known attack patterns since Oct 21. Origins reachable directly bypass the WAF; patching PHP is still required.

Check: Paid plans: Cloudflare Managed Ruleset deployed in block mode

AWS WAF

Core rule set SizeRestrictions_BODY for CVE-2026-109618 and PHP Managed Rule Group 2.3 for CVE-2026-109619. AWS: upgrading PHP is the only complete fix.

Check: WebACL uses SizeRestrictions_BODY and PHP rule group 2.3

Azure Front Door WAF

Managed rule 99006001 is rolling out (completion expected Oct 28) and is disabled by default; enable it. Upgrading PHP is the only full fix.

Check: Enable rule 99006001 (MS-ThreatIntel-Response-CVEs)

Google Cloud Armor

Google recommends managed rules (File Upload and RFI categories) plus a rule rejecting bodies over inspection limits. Not a replacement for patching.

Check: Review Cloud Armor preview/enforcement decisions in Cloud Logging

Imunify360 WAF

Rulesets 8.83–8.85 block the public exploit pattern for CVE-2026-109619 only; nothing covers CVE-2026-109618. Only the PHP update closes the flaws.

Check: imunify360-agent update --force modsec-rules

Sucuri WAF

Virtual-patching rules for known PHP2Shell paths; can miss variants and are bypassed if the origin is reachable directly. Install patched PHP and restart workers.

Check: Block direct origin access; verify the PHP version served

Wordfence

No firewall rule: some attack paths run before WordPress loads, so the application firewall cannot be relied on. Install patched PHP and restart it.

Check: WordPress Tools > Site Health > Info > Server

Interim mitigations

FAQ

Which PHP versions fix PHP2Shell?

PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released on October 21, 2026. Distribution and hosting-panel packages may carry the fix under a different version number, so compare against your vendor's fixed build.

php -v shows an older version on my server. Am I vulnerable?

Not necessarily. Debian, Ubuntu, RHEL and some hosting panels backport the fix without changing the upstream version string. Compare your package version with your vendor's row on this page. For php.net builds and the official Docker images, an older version means you are not patched.

Are PHP 7.4, 8.0 and 8.1 affected?

Officially the CVEs list 8.2–8.5, but the PHP team published source backports for 7.4, 8.0 and 8.1, which implies they are affected. These branches have no official release: rely on a vendor backport, apply the interim mitigations and upgrade.

Is the PHP CLI affected?

The advisory scopes the risk to installations serving web requests (FPM, mod_php, php-cgi, FrankenPHP, LiteSpeed). Patch the binary that serves traffic — check it with php-fpm -v or a phpinfo() page, not only php -v.

Is PHP2Shell exploited in the wild?

Yes. CISA added CVE-2026-109618 and CVE-2026-109619 to its Known Exploited Vulnerabilities catalog on October 26, 2026, which means it has evidence of active exploitation; US federal agencies must patch by October 29.

What is CVE-2026-115560? Is it part of PHP2Shell?

A separate, much less likely issue in session upload progress that php.net disclosed on October 23. It needs an application that switches session.serialize_handler to php at runtime. It will be fixed in the next regular release; until then set session.upload_progress.enabled=0, the same setting already listed as a PHP2Shell mitigation. The patch statuses on this page cover the two PHP2Shell CVEs only.

Do the interim mitigations make me safe?

No. The PHP team says the measures reduce exposure to specific attack paths but do not make an installation safe; updating is the only complete fix.

I use Docker. What do I need to do?

Pull the php base image again, rebuild every image built from it and redeploy. Supported tags (8.2–8.5) were rebuilt on October 21–22; the 8.1, 8.0 and 7.4 tags are no longer rebuilt and stay vulnerable.

Follow PHP releases

Security releases and breaking changes in one weekly email, or instantly on Telegram.

Use this tracker in your tooling

The vendor table is available as JSON (CC BY 4.0). Use it in scripts, dashboards or CI checks.

curl https://www.changes.watch/api/v1/advisories/php2shell

Sources

Found an outdated status? Tell us via contact — every row links to the vendor's own advisory.