The PHP project released urgent security updates on 19 November 2026 for every currently supported branch. Administrators should upgrade to PHP 8.2.36, 8.3.37, 8.4.28 or 8.5.13 as soon as possible. PHP 8.6.0, released on the same day, already contains the relevant fixes. The update is unusually important because the corrected defects include multiple paths that can lead to remote code execution, request smuggling, memory corruption and disclosure of sensitive data. PHP 8.1 and older branches are no longer supported upstream and do not receive these official fixes.
One of the most serious issues is CVE-2026-126714, a weakness in PHP’s default file-based session handler. An interrupted session write could leave old data at the end of a partially replaced session file. Under suitable application conditions, the resulting mixed session data could be interpreted as serialized objects and used to execute code through an available gadget chain. Another session-related flaw, CVE-2026-115560, involves applications that use different session serialization formats. These vulnerabilities make the update relevant even to otherwise ordinary PHP applications that rely on file-based sessions and upload progress.
PHP-FPM installations also require attention. CVE-2026-129289 concerns unread request-body data on persistent FastCGI connections. In configurations where a web server or proxy reuses backend connections, an unauthenticated attacker could potentially smuggle a second FastCGI request and execute PHP code with the permissions of the worker process. The releases also address several use-after-free and memory-safety problems in the PHP engine and extensions, including flaws affecting error backtraces and timezone handling. Not every application exposes every attack path, but the potential impact is high enough that configuration-based assumptions should not replace patching.
Before upgrading, confirm the PHP version actually used by each website in the hosting control panel or through a temporary diagnostic page; the command-line version shown by php -v may be different from the PHP-FPM version serving web requests. Install the fixed package supplied by the operating system or hosting vendor, then restart PHP-FPM and, where applicable, Apache. Test authentication, uploads, scheduled jobs and payment or API integrations after the restart. WordPress administrators should also verify that themes and plugins are compatible before moving to the new PHP 8.6 feature branch; installing the patched point release of the current supported branch is usually the lower-risk emergency action.
If an immediate update is impossible, temporary risk reduction can include disabling session upload progress and ensuring that FastCGI backend connection reuse is disabled. Applications can also avoid the vulnerable file-session path by using a properly secured alternative session backend. These are mitigations, not substitutes for installing a fixed PHP build. Administrators should inventory all active PHP runtimes, including separate pools and older versions kept for legacy sites, because updating one default binary does not automatically patch every website on the server.
Avots: Source: PHP official changelog
