TLDR;
The PHP critical security release on 19 November 2026 shipped PHP critical fixes across every supported branch and launched PHP 8.6.0 the same day. Here is what matters.
- New versions: PHP 8.5.13, PHP 8.4.28, PHP 8.3.37, PHP 8.2.36. PHP 8.6.0 was released on the same day as the next major branch.
- Fix counts: 18 CVEs in 8.5.13, 14 in 8.4.28, 13 in 8.3.37, and 12 in 8.2.36.
- PHP rates seven of the 8.5 fixes as Critical.
- Named flaws: CVE-2026-126714 (PHPAfterShell, PHP session TOCTOU), CVE-2026-115560 (PHP RCE vulnerability in session upload progress), CVE-2026-129481 (PHP2Shell incomplete fix, PHP session use-after-free), CVE-2026-129289 (PHP-FPM request smuggling), CVE-2026-129496, CVE-2026-129474, CVE-2026-129182 (use-after-free flaws).
- Exploitation status: no in-the-wild reports for the November CVEs. The October PHP2Shell CVEs (CVE-2026-109618 and CVE-2026-109619) are in CISA KEV and used in active attacks.
- Action: Upgrade to the fixed release on your PHP branch and restart PHP workers.
PHP is a server-side scripting language that runs a large share of production web applications, almost 70% of the internet runs on it. After PHP2Shell in October and the month of patch chaos that followed, PHP has come back with another round. The PHP critical security release on 19 November 2026 covers every supported branch: PHP 8.5.13, PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. PHP 8.6.0 launched the same day as the next major branch.
The PHP project labels seven of the 8.5 fixes Critical and notes that most critical issues require non-default configuration. One of the new flaws, CVE-2026-129481, is listed by PHP as an incomplete fix for CVE-2026-109619, meaning October’s PHP2Shell patch did not fully close the hole.
Technical Details of the PHP Critical Fixes
The release clusters around session handling, memory safety, and PHP-FPM.
Session handling and RCE: CVE-2026-126714 (PHPAfterShell) is a TOCTOU in PHP’s file-based session storage: pwrite() followed by ftruncate() is non-atomic, so an interrupted write leaves mixed bytes that the PHP session deserializer later turns into an object injection primitive. CVE-2026-115560 is a separate PHP RCE vulnerability in session upload progress that PHP flagged in October without a patch. CVE-2026-129481 is a PHP session use-after-free and an incomplete fix for CVE-2026-109619 (PHP 8.3 and later).
Memory safety: CVE-2026-129496 is a use-after-free rated CVSS 9.2. CVE-2026-129474 is a use-after-free in magic method backtraces that can lead to remote code execution (8.5 only). CVE-2026-129182 is a use-after-free via repopulation of last_fatal_error_backtrace after shutdown (8.5 only). CVE-2026-129501 is a double free during DOM XML serialization (8.4 and 8.5).
PHP-FPM and extensions: CVE-2026-129289 is PHP-FPM HTTP request smuggling through an unread HTTP body (also reachable as php://input request smuggling). CVE-2026-129291 is an epoll use-after-free in PHP-FPM that enables local privilege escalation. CVE-2026-129292 is XSS in the PHP-FPM status endpoint. CVE-2026-128090 is a PHAR OpenSSL signature bypass through algorithm downgrade. CVE-2026-129506 and CVE-2026-15353 are SOAP flaws.
Affected Products or Versions
The release covers PHP’s reference implementation on every supported branch. Some CVEs only affect the newer branches. Non-file session handlers are safe from the two session-handling RCE paths.
- PHP 8.5 before 8.5.13. Fixed in 8.5.13.
- PHP 8.4 before 8.4.28. Fixed in 8.4.28.
- PHP 8.3 before 8.3.37. Fixed in 8.3.37.
- PHP 8.2 before 8.2.36. Fixed in 8.2.36. PHP 8.2 reaches end of life on 31 December 2026.
- PHP 8.1 and earlier are end of life and will not receive these fixes.
- The October 21 releases (8.5.12, 8.4.27, 8.3.36, 8.2.35) do not contain these fixes.
Detection
Start from the PHP version actually serving web traffic in production, since a repository’s declared version can differ from the deployed runtime. Then confirm which optional components are enabled.
- Run
php -von each web host or container and compare with the fixed versions above. - Check
php.iniforsession.save_handler. A value offiles, or no value set, puts the host in scope for CVE-2026-126714. - Check
php.iniforsession.upload_progress.enabled. A value of1, or no value set, opens the session upload progress attack path. - Confirm whether PHP-FPM, PHAR, SOAP, or DOM extensions are loaded and reachable from untrusted input.
- Inspect container images and Docker build pipelines for pinned PHP minor versions below the fixed releases.
- No reliable indicators of compromise have been published for the November fixes.
Mitigation
Install the PHP remote code execution patch for your branch: 8.5.13, 8.4.28, 8.3.37, or 8.2.36. On Ubuntu and Debian, pull the fixed package from the security repository and restart PHP workers (systemctl restart php-fpm or the SAPI in use). On Docker, rebuild images on a fixed base tag such as php:8.5.13-fpm or php:8.4.28-apache and redeploy so every long-lived process picks up the new binary. If you run PHP 8.1 or earlier, move to a supported branch, since those versions will not get this fix.
Workaround
If an immediate upgrade is not possible, reduce exposure by disabling the optional components the critical flaws depend on. Treat these as interim measures only.
- Set
session.upload_progress.enabled = 0inphp.iniand restart PHP workers. - Switch
session.save_handlerto a non-file backend such as Redis or a database for affected hosts. - Restrict network access to PHP-FPM status endpoints to trusted networks.
- Avoid processing untrusted PHAR archives and untrusted SOAP input until the upgrade is complete.
How Astra Helps
We are monitoring the situation and will update this page once more information comes in. If you need help or guidance on the PHP critical security release, talk to our team.
References: PHP November 2026 security release notes (php.net, 19 November 2026); PHP GHSA advisories per CVE; CISA KEV catalog for CVE-2026-109618 and CVE-2026-109619.



