PHP 8.5.13: FPM Request Smuggling RCE - Floor 8.5.13 / 8.4.28

PHP shipped a security release on 19 November 2026: 8.5.13, 8.4.28, 8.3.37, 8.2.36. The changelog and GitHub Security Advisories list 17 issues. Seven are GitHub-rated Critical with CVSS 4.0 score 9.2. The one that matters on a shared box first is CVE-2026-129289: PHP-FPM can fail to drain an unread HTTP body on a reused FastCGI connection, so leftover bytes become a second FastCGI request the front end never authorized.[1][2][3]
That is unauthenticated code execution as the PHP worker when the front end keeps the backend connection open and the app opens php://input without reading it to the end. Standard nginx/Apache that close FastCGI after each request are not in the demonstrated FPM attack. LSAPI can desync; PHP does not claim RCE on LSAPI for this CVE.[3]
This is not PHP2Shell (CVE-2026-109618 / 109619, 21 Oct). Two of today's Criticals are follow-ups to that work. CVE-2026-115560 (session serializer mismatch) is the upload-progress path PHP told operators to disable in October; it now has a CVE and a 9.2 score.[5][7][9]
Not on CISA KEV. Catalog 2026.11.20, 1,790 entries, dateReleased 2026-11-20T17:48:39.1516Z. Newest KEV rows are Apache Roller, VMware vCenter, SAP NetWeaver, Cisco Expressway - not PHP.[10]
If you run PHP-FPM, LiteSpeed lsphp, Plesk handlers, or CloudLinux alt-php/ea-php, this is today's version floor.
What it is
Vendor-published facts:
- php.net: security releases for all supported 8.x on 19 Nov 2026. Pre-announce (18 Nov) said highest severity CRITICAL, and that Critical issues require either non-default configuration or uncommon setups.[1]
- Changelog 8.5.13 names the GHSAs/CVEs. The list differs by branch - read the changelog for your minor, not a tweet-sized dump.[2]
- CVE-2026-129289 (GHSA-qc49-hpvq-g2w6): lazy
php://inputsince PHP 5.6.0. On FPM withFCGI_KEEP_CONN, unread body bytes can be parsed as a new FastCGI record. Forged params can includeSCRIPT_FILENAME,REMOTE_ADDR,PHP_ADMIN_VALUE. GitHub Critical, CVSS 4.0 9.2 (AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H).[3] - CVE-2026-126714: default
filessession handler can leave a split file after an interrupted write; nextsession_start()may deserialize attacker-controlled objects if the app has a gadget chain. Critical, 9.2.[4] - CVE-2026-115560: session upload progress writes one serializer, a later reader uses another (
php_binary/php_serializevsphp). Critical, 9.2. Needs upload progress on (PHP default is on) plus a serializer mismatch plus a gadget chain.[5] - CVE-2026-129291: FPM epoll UAF when
catch_workers_outputis on. Worker code → FPM master (often root). GitHub High, CVSS 4.0 8.8, local (AV:L).[6] - Other Critical 9.2s: timezone-cache UAF CVE-2026-129496; interrupted session shutdown UAF CVE-2026-129481 (8.3+; incomplete fix for 109619); magic-method backtrace UAF CVE-2026-129474 (8.5,
fatal_error_backtraces=1andzend.exception_ignore_args=0).[7][12][13] - CVE-2026-129182: shutdown backtrace UAF on 8.5 after a fatal diagnostic during later shutdown work. Critical, 9.2.[14]
We did not send a smuggled FastCGI record or interrupt a session write. Do not paste a "how to reproduce" into a ticket.
This is not:
- CVE-2026-109618 / 109619 (21 Oct PHP2Shell). Patching to 8.5.12 does not make 8.5.13.
- WordPress 7.1.4 / 7.1.5. Core updates do not replace
php-fpm. - cPanel 138.0.25 WP Toolkit proxy (18 Nov) or 138.0.28 reseller-SSL TSR (19 Nov). Those are panel floors. This is the PHP binary.
How serious is it?
PHP rated seven issues Critical at 9.2. CloudLinux's 20 Nov advisory counts the same 17 GHSAs and the same seven Criticals.[9]
Take the pre-announce at its word: Critical needs a setup. Then read which setup:
- 129289 needs backend keep-alive (
nginx fastcgi_keep_conn on, Apachemod_proxy_fcgienablereuse=on, HAProxy FastCGI reuse, or LSAPI persistence) and a path that opensphp://inputwithout draining it. Default nginxfastcgi_keep_connis off. If you turned keep-alive on for FPM performance, you are in the demonstrated FPM RCE class until the binary is new.[1][3] - Session RCEs need gadgets in the application. WordPress/Laravel/Symfony are not automatically "has a gadget"; we are not claiming a public gadget for a named CMS. Absence of a named gadget is not "safe."[4][5]
- 129291 needs code execution in a worker already, then
catch_workers_output. Treat it as tenant-to-root on FPM, not as an unauth internet 9.8.[6]
No in-the-wild statement from php.net or the GHSAs we used. Not KEV. Absence from KEV is not "scanners will wait."[10]
Who is affected
In scope:
- php.net supported: anything below 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36.[1][2]
- Plesk Obsidian: panel engine
sw-engine/plesk-engineuntil 18.0.81 Update 9 or 18.0.82 Update 4. Client PHP floors: 8.5.13, 8.4.28, 8.3.37, 8.2.36; Plesk-backported 8.1.34, 8.0.30, 7.4.33. Plesk also notes those panel updates ship NGINX 1.30.7 (CVE-2026-123007) - separate bug, same updater.[8] - CloudLinux alt-php (Selector): alt-php85 8.5.13-1 through alt-php82 8.2.36-1, plus backports on 5.2-8.1 (e.g. alt-php81 8.1.34-43, alt-php74 7.4.33-84). ea-php in
cl-ea4: ea-php85 8.5.13-1, ea-php84 8.4.28-1, ea-php83 8.3.37-1, ea-php82 8.2.36-1, older trains by release suffix (ea-php81 8.1.35-2.cloudlinux.2, and so on). Native OSphpon CL 8/9/10: CloudLinux's 20 Nov 12:03 UTC TL;DR still said beta, not stable. Do not assumednf upgradeon stable installed native php.[9][11]
Out of scope unless your vendor said so:
- PHP 8.1 and older at php.net - no php.net tarball. Plesk and CloudLinux published backports; vanilla distro 8.1 may not. Upgrade the branch or isolate.[1][8][9]
- A site on 7.1.5 WordPress with an old
lsphp. The CMS version is the wrong column.
What to do now
- Read the binary that serves the site, not
phpon root's PATH.
php -v
# cPanel EA4 examples:
/opt/cpanel/ea-php82/root/usr/bin/php -v
/opt/cpanel/ea-php83/root/usr/bin/php -v
# Plesk:
/opt/plesk/php/8.3/bin/php -v
# CloudLinux alt-php:
/opt/alt/php82/usr/bin/php -v
rpm -q alt-php82-common ea-php82-php-cli 2>/dev/null
Want 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36 on current trains, or the CloudLinux/Plesk backport NEVRA above. 8.5.12 is last month.
- Patch, then restart workers. A new rpm with old FPM still running is not a patch.
# CloudLinux Selector
dnf clean all && dnf upgrade 'alt-php*'
# CloudLinux cPanel EA4
dnf clean all && dnf upgrade 'ea-php*'
# CL7: yum clean all && yum update 'alt-php*' / 'ea-php*'
/scripts/restartsrv_httpd
/scripts/restartsrv_apache_php_fpm
# Plesk panel + handlers
plesk installer update
systemctl restart plesk-php*-fpm 2>/dev/null
# LiteSpeed
systemctl restart lsws
-
Until the new binary is in the worker: PHP's documented FPM mitigation is stop reusing the backend connection - leave nginx
fastcgi_keep_connoff, leave Apacheenablereuseoff. That closes the demonstrated 129289 FPM path. It does not fix session UAFs or 129291.[3] -
Keep
session.upload_progress.enabled=0in a system ini / FPM admin value (not.user.ini) until you have confirmed the new build. That was the October stop-gap for 115560; the November binary is the fix. Leaving it off is still fine.[5][9] -
If
catch_workers_outputis on, know 129291 is in play until FPM is new. Do not turn it on as a "debug leftover" on shared boxes.[6] -
Shared and reseller first. FPM pools that serve many accounts with keep-alive are the queue. Single-owner VPS still patch; the worker is still the site.
Versions with no php.net floor
8.1 and older - php.net will not ship 8.1.34. Plesk listed 8.1.34 / 8.0.30 / 7.4.33 backports. CloudLinux listed alt-php/ea-php backports through 5.2. If your vendor has no row, upgrade the branch or take the site off the internet. A WAF is not a PHP binary.[8][9]
EOL 5.x / 7.2 / 7.3 without a paid ELS vendor: isolate, then migrate. TuxCare ELS is what Plesk named for 5.6/7.2/7.3 - we did not verify those packages in this run.[8]
Compromise signs
None of these prove 129289 by themselves.
- PHP/FPM/LiteSpeed workers spawning shells,
curl,wget, or unexpectedphp -rafter 19 Nov. - New PHP files under docroots /
upload/wp-contentdated after the release that you did not deploy. - FPM master (
php-fpm, often root) with unexpected children or new cron whilecatch_workers_outputwas on. php -vstill on 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35 (PHP2Shell floor) after you thought November landed.
The GHSAs publish no log signature. Do not grep for a path we invented.
FAQ
Is this PHP2Shell again? No. PHP2Shell was 109618/109619 on 21 Oct. Today's release includes follow-ups (129481, 129182) and the 115560 upload-progress CVE that had no patch in October.[5][7][9]
Did PHP say Critical needs a weird config? Yes, in the 18 Nov pre-announce. 129289's "weird" is FastCGI keep-alive. If you never enabled it, you are outside the demonstrated FPM RCE. Check nginx/Apache anyway; do not assume.[1][3]
Does LiteSpeed get RCE from 129289? PHP: LSAPI can leave body bytes and desynchronise. They do not establish arbitrary code execution on LSAPI. Still patch lsphp.[3]
Is it on KEV? No. Catalog 2026.11.20 / 1,790.[10]
Does upcp to 138.0.28 fix this? No. That is cPanel's 19 Nov reseller-SSL TSR. PHP is ea-php / alt-php / lsphp / plesk php. Check php -v on the handler.
Can I leave upload_progress off after patching? Yes. The binary is the fix for 115560; the ini is optional hardening.[5]
What we are not claiming
- We did not exploit smuggling, session split-writes, or FPM epoll UAF.
- No in-the-wild / ransomware statement from php.net or these GHSAs.
- No CVSS v3 on the GitHub objects we pulled - scores above are CVSS 4.0 from
cvss_severities.cvss_v4. - We did not inventory every distro (Remi, Sury, Ubuntu
php8.3). Use their changelog. - CloudLinux native
phpon 8/9/10 was beta in the 20 Nov 12:03 UTC advisory TL;DR. Status-page "all packages released" on 20 Nov 12:14 UTC listed alt-php / ea-php. Do not flatten those.[9][11] - Plesk NGINX 1.30.7 / CVE-2026-123007 is in the same Plesk updater, not this PHP bug.[8]
Sources
[1] https://www.php.net/archive/2026.php [2] https://www.php.net/ChangeLog-8.php [3] https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6 [4] https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp [5] https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx [6] https://github.com/php/php-src/security/advisories/GHSA-jm4m-qfqx-967m [7] https://github.com/php/php-src/security/advisories/GHSA-g3vh-838c-65v7 [8] https://support.plesk.com/hc/en-us/articles/45146523211671-Critical-PHP-Security-Release-on-19-Nov-2026 [9] https://cloudlinux.com/security/php-november-2026-security-releases [10] https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json [11] https://status.cloudlinux.com [12] https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv [13] https://github.com/php/php-src/security/advisories/GHSA-8mjj-2r7p-4hg2 [14] https://github.com/php/php-src/security/advisories/GHSA-2fjv-p558-g82m