Resources › CVE intelligence › PHP2Shell

PHP2Shell

CVE-2026-109618 · CVE-2026-109619

Exploited · CISA KEV Component: PHP Updated 19 November 2026

Verdict

Unauthenticated remote code execution in the PHP engine. Any PHP that takes input from the network and runs a build without the complete patch is exposed. PHP's first patch (21 October) was incomplete on 8.3 to 8.5: you're fully patched at 8.2.35, 8.3.37, 8.4.28 or 8.5.13, or a distribution build that carries both rounds. Your php.ini settings reduce exposure; none of them makes a server safe.

Does it reach you?

Exposed = both hold. If either is false for a machine, it's out.

RequirementHow to check itRules a machine out when
1. The PHP build lacks the complete patchYour package's changelog for the CVE IDs (commands below), not the version stringThe build carries both rounds: upstream 8.2.35 and later on 8.2, 8.3.37, 8.4.28 or 8.5.13 and later, or a distribution package with both. Several distributions ship the patch under older version numbers
2. That PHP takes input from the networkss -ltnp | grep -E 'php-fpm|apache2|httpd|frankenphp|lsphp'PHP runs only from the command line on local data (build images, local cron jobs). PHP serving web requests (mod_php, PHP-FPM, php-cgi, FrankenPHP, LiteSpeed) and long-running workers that process network data stay in scope

Not required, so these don't rule a machine out: a multipart request (an ordinary form POST reaches the bug), a finite memory_limit (a real allocation failure takes the same path), mod_php (PHP confirms code execution on PHP-FPM), session upload progress being on (CVE-2026-129481 doesn't need it), or one request per worker.

Are you actually fixed?

Fixed versions by build. Where a version number misleads, the row says so.

BuildStatus as of 19 November 2026
Upstream 8.2.35 and later; 8.3.37, 8.4.28, 8.5.13 and laterFixed
Upstream 8.3.36, 8.4.27, 8.5.12 (the 21 October releases)Fixed for the 21 October advisories; a critical route is still open: CVE-2026-129481, and on 8.5 also CVE-2026-129182. Update to 8.3.37, 8.4.28 or 8.5.13. Distribution rows below show fixes for the 21 October advisories; on 8.3 to 8.5, check that your package also carries the 19 November fixes
Docker official php images 8.2.36, 8.3.37, 8.4.28, 8.5.13 (updated 19 November)Fixed
Debian 13 trixie php8.4 8.4.27-1~deb13u1 (DSA-6574-1); Debian 12 bookworm php8.2 8.2.35-1~deb12u1 (DLA-4848-1); forky and sid php8.4 8.4.27-1Fixed; Debian has also shipped the 19 November releases (bookworm 8.2.36-1~deb12u1, trixie 8.4.28-1~deb13u1)
Ubuntu 24.04 php8.3 8.3.6-0ubuntu0.24.04.13; Ubuntu 22.04 php8.1 8.1.2-1ubuntu2.28; 26.04 php8.5 8.5.4-0ubuntu1.5; 26.10 php8.5 8.5.9-0ubuntu2.1 (USN-8948-1/-2)Fixed, under version numbers that tools reading the upstream PHP version flag as vulnerable
Ubuntu Pro (ESM): php7.4 (20.04), php7.2 (18.04), php7.0 (16.04), php5 (14.04)Fixes released
Chainguard and Wolfi php-8.2 8.2.34-r4, php-8.3 8.3.35-r4, php-8.4 8.4.26-r4, php-8.5 8.5.11-r4Listed fixed, under version numbers below the upstream fix
Alpine edge, v3.24 and v3.23: php83 8.3.36-r0, php84 8.4.27-r0, php85 8.5.12-r0; v3.22: php82 8.2.35-r0, php83 8.3.36-r0, php84 8.4.27-r0; v3.21: php82 8.2.35-r0Fixed (older Alpine branches: no fix recorded as of this date)
RHEL 8 php:7.4, php:8.2; RHEL 9 php, php:8.2, php:8.3; RHEL 10 php, php8.4 (RHSA-2026:87070, 87071, 87072, 87073, 87079, 87080, 87151); Oracle Linux 8, 9 and 10 (ELSA-2026-87070, -87071, -87072, -87073, -87079, -87080, -87151); AlmaLinux 8, 9 and 10 (ALSA-2026:87070, :87071, :87072, :87079, :87080)Fixed packages released
RHEL 9 php:8.4Fixed (RHSA-2026:97880, 10 November). Red Hat says it is expediting the 19 November fixes
RHEL 7 (PHP 5.4)Fixed for CVE-2026-109619 under Extended Life Cycle Support: php 5.4.16-48.el7_9.1 (RHSA-2026:88693, 23 October), and Oracle Linux 7 (ELSA-2026-88693, 29 October); not affected by CVE-2026-109618. The fixed package still reports PHP 5.4.16, so tools reading the upstream version flag it as vulnerable
Amazon Linux 2023 php8.2, php8.3, php8.4, php8.5 (ALAS2023-2026-3301/3302/3303/3304); Amazon Linux 2 php8.2 (ALAS2PHP8.2-2026-015); Amazon Linux 2027 php8.5 (ALAS2027-2026-243)Fixed packages released; each advisory lists both CVEs
Amazon Linux 2 base php; AL2023 php8.1No fix planned (Amazon)
SUSE SLE 15 SP7 (php7, php8), SLES 16.0, SLE 15 SP4 to SP6 LTSS, SLE 12 SP5 php74 (SUSE-SU-2026:4843-1, 4844-1, 4852-1, 4853-1, 4870-1, 24271-1); bci/php, bci/php-apache and bci/php-fpm 8.3.36 imagesFixed; also fixed in SLES 16.1 (php8 8.5.12), openSUSE Leap 16.0 and openSUSE Leap 16.1. The bci/php:8-micro image fix is in progress; SUSE lists openSUSE Leap 15.x and SUSE Manager 4.x, both past end of life, as affected
Palo Alto Networks PAN-OS 10.2, 11.1, 11.2, 12.1 and 12.2 (PA-Series and VM-Series firewalls, Panorama)Fixed hotfix releases for each branch, released 25 to 29 October (Palo Alto Networks advisory); exploited through management interfaces exposed to the internet. PHP's version numbers don't apply; check the PAN-OS version
Cisco (selected products, including Duo Access Gateway and Expressway Series); Citrix NetScaler ADC and NetScaler Gateway; F5 BIG-IP APM and the BIG-IP Configuration utility; Siemens RUGGEDCOM APE1808 (runs PAN-OS, SSA-566512)Affected, per Singapore's Cyber Security Agency (AL-2026-157, 3 November), which says the list is not exhaustive; the fixed versions are in each vendor's advisory. Singapore's list now also names Fortinet, which rates its own exposure as denial of service only and not exploited
Check Point Security Gateways using the Mobile Access portal and the other web features listed in sk1000302Exploited from 30 October through the Mobile Access portal, with root through CVE-2026-123039 (Check Point Research); some targets were wiped. Fixed in Jumbo Hotfix takes R81.20 T174, R82 T132, R82.10 T52 and R82.20 T14 (sk1000302); management servers aren't affected. PHP's version numbers don't apply
QNAP QTS, QuTS hero and QuTScloudFixed (QNAP security update); check QNAP's advisory for the fixed builds
Azure App Service and Azure Functions (PHP that Microsoft runs)Updated by Microsoft. The built-in PHP runtimes on App Service for Windows are end of life: Microsoft says to move those apps to App Service on Linux or bring a supported PHP runtime
Other products that embed PHPCheck the vendor. The Dutch NCSC tracks 948 products: 185 fixed and 215 vulnerable as of 4 November
PHP 7.4, 8.0, 8.1 from php.netNo official release; PHP published source backports only
PHP 5.4 to 7.3End of life, no fix from PHP

Check your own build

# Debian / Ubuntu: is the fix in the installed package?
# On 8.3 to 8.5, also look for CVE-2026-129481 (and CVE-2026-129182 on 8.5)
zgrep -E 'CVE-2026-(10961[89]|129481|129182)' /usr/share/doc/php*/changelog.Debian.gz

# RHEL / Fedora / Amazon Linux / Oracle Linux (package names vary: php-common, php8.4-common, ...)
rpm -qa 'php*common*' | xargs -n1 rpm -q --changelog | grep -E 'CVE-2026-(10961[89]|129481|129182)'

# Alpine / Wolfi / Chainguard: compare with the fixed versions above
apk info -v | grep -E '^php'

# Anything else: the version, then your vendor's advisory
php -v

An empty result isn't proof you're vulnerable: some changelogs cite only the advisory ID (DSA, USN, RHSA). If in doubt, compare your package version with your vendor's advisory. To see which PHP processes take network input:

ss -ltnp | grep -E 'php-fpm|apache2|httpd|frankenphp|lsphp'

What holds until you patch

Each of these lowers risk while you patch. None makes a server safe, and PHP's advisory says the same. Set them in configuration that loads before request parsing (php.ini, the FPM pool, server config), then restart every worker.

WorkaroundWhat it coversWhy it isn't enough
session.upload_progress.enabled=0The confirmed upload-progress route of CVE-2026-109619; fully covers CVE-2026-115560 on builds older than the 19 November releasesPHP: it "blocks the confirmed session paths but not other variants". The other routes, CVE-2026-109618 and CVE-2026-129481 don't need it
memory_limit=-1The memory-limit trigger of CVE-2026-109618PHP: "an underlying allocation failure can still reach the vulnerable path"; it also removes your protection against one request using all memory
fatal_error_backtraces=0 (8.5)One confirmed producer on PHP 8.5Covers that path only
pm.max_requests=1Each FPM worker handles one request, which breaks the confirmed cross-request sequencePHP: recycling lowers success rates but doesn't remove the condition
Running PHP-FPM instead of mod_phpSome startup routesPHP confirms CVE-2026-109619 code execution on FPM
Lower post_max_size, input limits, WAF rulesSome request shapesRequests without a declared length and other shapes get around them; a WAF must inspect full bodies and field names. AWS's managed PHP rule group has a rule for each CVE from version 2.4, and AWS calls its coverage of the out-of-memory trigger partial: inspection stops at the body inspection limit

What's happening now

  • 19 November: PHP calls CVE-2026-129481 "an incomplete fix for CVE-2026-109619" (PHP 8.3 and later) and publishes CVE-2026-129182 on 8.5; both are critical and patched in 8.3.37, 8.4.28 and 8.5.13. The same releases patch the related CVE-2026-115560 and turn session upload progress off by default.
  • Exploited in the wild: on Palo Alto Networks PAN-OS firewalls exposed to the internet, and from 30 October on Check Point gateways through the Mobile Access portal, both chained with a kernel or appliance flaw for root. CISA added both CVEs to its Known Exploited Vulnerabilities catalog on 26 October.
  • Broad attempts: GreyNoise counts 1,304 confirmed successful exploitations of its deliberately vulnerable sensors from 25 attacker addresses, through 17 November. Censys's version-based count of affected internet-facing services fell from 29.3 million to 26.5 million.
  • Before disclosure: Amazon's honeypots recorded an exploitation attempt on 17 October, four days before PHP's advisories. Investigate from that date, not the disclosure date.

The full story, including how we confirmed each point: PHP2Shell: what actually decides whether you're exposed →

Updates

  • 19 November 2026: published, refreshed against our sources. PHP's 19 November releases complete the fix for CVE-2026-109619 (CVE-2026-129481 on 8.3 and later, CVE-2026-129182 on 8.5); exploitation on Check Point gateways added.

Sources