PHP announced PHP 8.5.13 as a security release, and BleepingComputer reported that updates for PHP branches 8.2–8.5 were released on November 19, 2026. If you maintain a site, identify the PHP runtime serving it and apply the update for that branch. PHP’s release announcement confirms 8.5.13 and encourages PHP 8.5 users to upgrade.
Treat the upload-progress setting as a targeted mitigation for CVE-2026-115560, then apply the security release for the runtime serving your site.
Which PHP version should you install?
PHP’s development team identifies PHP 8.5.13 as a security release. BleepingComputer and SecurityWeek reported these patch versions for the branches in the November update:
| PHP branch | Reported patch version |
| 8.2 | 8.2.36 |
| 8.3 | 8.3.37 |
| 8.4 | 8.4.28 |
| 8.5 | 8.5.13 |
The November release is separate from October’s PHP2Shell fixes, covered in NeoTeo’s report on the earlier PHP patches.
When does the PHP-FPM request-smuggling risk apply?
CVE-2026-129289 is a PHP-FPM request-smuggling flaw. BleepingComputer and The Hacker News describe a remote-code-execution path that depends on persistent backend connection reuse and request-body handling. In the described scenario, an application opens php://input without fully reading it, allowing unread request-body bytes to form a separate FastCGI request. Those reports say standard nginx and Apache setups without backend connection reuse are unaffected by this specific path.
Another reported issue, CVE-2026-126714, involves interrupted writes to file-based session data. SecurityWeek and The Hacker News describe a code-execution path that also depends on an attacker influencing session data and the application having a suitable deserialization gadget chain.
Check the PHP runtime serving your site
Check the PHP version used by the public-facing site, then apply the corresponding update through whoever manages that runtime: your hosting provider, distribution or deployment team. A workstation’s command-line PHP can be a different installation from the runtime serving the site, a distinction noted in Infobae’s administrator guidance.
What does the upload-progress mitigation cover?
PHP’s archive describes a specific configuration for CVE-2026-115560: session upload progress is enabled, session.serialize_handler is configured as php_binary or php_serialize, and application code switches the handler to php at runtime with ini_set() before session_start(). PHP’s advisory says setting session.upload_progress.enabled=0 addresses that particular exposure. It does not cover every issue in the November update.
PHP also says applications that do not switch the session handler at runtime can leave upload progress enabled.