Severity
Critical
CVSS
9.2 (CVSS v4.0)
Status
No known exploitation
Fix
Patch available
Affected
PHP before 8.2.36, 8.3.37, 8.4.28 and 8.5.13; end-of-life versions may also be affected

PHP released 8.2.36, 8.3.37, 8.4.28 and 8.5.13 on 19 November 2026, fixing eight vulnerabilities in the PHP runtime. Seven are rated 9.2 (CVSS v4.0), and the eighth, a local privilege escalation in PHP-FPM, is rated 8.8. Most of them can lead to code execution as the account the PHP worker runs under.

The conditions for exploitation differ from one flaw to the next, and several depend on how the server or application is configured. Three can be exploited by a remote attacker without credentials where those conditions are met: CVE-2026-129496, CVE-2026-129289 and, on PHP 8.5, CVE-2026-129474.

Update to PHP 8.2.36, 8.3.37, 8.4.28 or 8.5.13. PHP 8.6.0 also includes the fixes. Until you can update, configuration changes can block six of the eight, as described under mitigation.

Exploitation status

We are not aware of exploitation in the wild or a public proof of concept for any of the eight vulnerabilities at the time of writing.

That can change quickly: exploitation of the PHP2Shell vulnerabilities patched in October was reported within a day of their details becoming public.

Who is affected

The flaws are in PHP itself, so any application running on an affected version is exposed, whether that's WordPress, Magento or an in-house application. Whether a particular server can be exploited depends on the flaw.

Some are limited to certain branches, some need a particular front-end or session configuration, and some need an object gadget chain in the application's code. The exploitation conditions table sets out each one.

Affected and fixed versions

BranchAffectedFixedVulnerabilities fixed
8.28.2.0 to 8.2.358.2.365
8.38.3.0 to 8.3.368.3.376
8.48.4.0 to 8.4.278.4.286
8.58.5.0 to 8.5.128.5.138

Four of the vulnerabilities affect every release on all four branches. The others are narrower:

  • CVE-2026-129182 and CVE-2026-129474: PHP 8.5 only.
  • CVE-2026-129481: PHP 8.3, 8.4 and 8.5.
  • CVE-2026-129291: PHP 8.2 from 8.2.7 onwards, and every release before the fixed version on 8.3, 8.4 and 8.5.

PHP 8.1 and older are end-of-life and receive no official fixes. The advisories only list supported branches, so an older version being absent from them doesn't mean it is unaffected. Check your operating system vendor or hosting provider for backported packages.

Exploitation conditions

The table lists the conditions each vulnerability requires before it can be exploited. Updating fixes all eight.

CVEBranchesConditions
CVE-2026-1294968.2 to 8.5No credentials. A non-thread-safe build (FPM, mod_php or CGI) logging to a file via error_log, and a startup warning such as an invalid date.timezone or a session configuration warning
CVE-2026-1155608.2 to 8.5Session upload progress enabled (the default), session data decoded in a different format to the one it was written in, and a gadget chain in the application
CVE-2026-1292898.2 to 8.5No credentials. Persistent FPM or LSAPI connections (e.g. nginx fastcgi_keep_conn on) and a route that doesn't read the full request body
CVE-2026-1291828.5A fatal error during shutdown, then another request on the same worker
CVE-2026-1294748.5No credentials. zend.exception_ignore_args = 0 (php.ini-production sets 1) and a fatal error inside a __call() method
CVE-2026-1294818.3 to 8.5An interrupted session shutdown, then another request on the same worker
CVE-2026-1267148.2 to 8.5Influence over session contents, an interrupted session file write and a gadget chain in the application
CVE-2026-1292918.2.7 to 8.5Code execution in an FPM worker, catch_workers_output enabled (off by default, on in the official PHP-FPM Docker images) and the epoll event backend. Leads to the privileges of the FPM master, often root

Mitigation

Updating is the only complete fix. Install PHP 8.2.36, 8.3.37, 8.4.28 or 8.5.13, or a package from your operating system vendor or hosting provider with the fixes backported, starting with internet-facing servers.

Configuration workarounds

These settings don't replace updating

Each of these settings blocks one or two specific vulnerabilities and must not be used in place of updating. There is no workaround listed here for CVE-2026-129496 or CVE-2026-126714.

Set them in php.ini, the PHP-FPM pool configuration or the Apache server configuration, so that applications can't override them with ini_set(). Restart every PHP worker afterwards so they take effect.

CVE-2026-129289: persistent FastCGI connections

This one is set on the web server in front of PHP rather than in PHP itself. Turn off backend connection reuse so that each request gets a fresh connection to PHP-FPM or LSAPI. For nginx, set fastcgi_keep_conn to off (the default), or remove the directive:

fastcgi_keep_conn off;

For Apache mod_proxy_fcgi, leave enablereuse off. Other FastCGI front ends should be configured to close the backend connection after every request. PHP-FPM and LSAPI listeners should not be exposed directly to untrusted networks.

CVE-2026-115560: session upload progress

Turn off session upload progress:

session.upload_progress.enabled = 0

Before turning it off, check that none of your applications use upload progress, for example to show a progress bar during file uploads.

CVE-2026-129182 and CVE-2026-129474: fatal error backtraces (PHP 8.5)

Turning off fatal error backtraces blocks CVE-2026-129182 and the attack path for CVE-2026-129474. As both vulnerabilities only affect PHP 8.5, this setting covers every affected installation:

fatal_error_backtraces = 0

For CVE-2026-129474, setting zend.exception_ignore_args also works:

zend.exception_ignore_args = 1

CVE-2026-129481: worker recycling in PHP-FPM

For PHP-FPM, set each pool to recycle its workers after a single request, so that a worker affected by a failed session cleanup doesn't serve another request:

pm.max_requests = 1

Starting a new worker for every request adds overhead, so check the performance impact before applying it to busy pools.

CVE-2026-129291: worker output capture in PHP-FPM

Turn off catch_workers_output in affected pools. The official PHP-FPM Docker images turn it on, so check container builds as well as servers.

catch_workers_output = no

Worker output is then no longer written to the FPM log, so check whether your logging relies on it. Running the FPM master process as a user other than root also limits the privileges an attacker can gain through this vulnerability, although it doesn't fix the underlying flaw.

Update log

19 November 2026

Initial publication.

References