On November 19, 2026, PHP published fixes for two flaws with different consequences. CVE-2026-129291 can give someone already running code in a PHP-FPM worker the privileges of its master process on certain installations. CVE-2026-129496 affects timezone handling: a remote request can crash a vulnerable process, and code execution is possible under additional conditions. If you manage a VPS, check the PHP runtime serving the website, not just the one in your shell.
PHP-FPM: can one site gain root privileges?
PHP-FPM usually separates the master process that manages the service from the workers that execute each site's code. This flaw affects that boundary. On Linux, relevant configurations use epoll and capture worker output with catch_workers_output. Standard FPM disables this setting by default, but the official PHP-FPM Docker images enable it. Check the effective configuration of your image or pool.
The key prerequisite is existing code execution in an FPM worker. Visiting the website is not enough. The privileges at stake are those of the master process; if that means root inside a container, it does not establish root access to the host. PHP rates this issue High, 8.8 on CVSS 4.0. PHP advisory for CVE-2026-129291.
The timezone cache: what has actually been demonstrated?
The second flaw is not limited to FPM. PHP can retain a reference to freed memory when a startup warning is written to a PHP error log file. Another diagnostic early in a request in a fresh worker can then cause the process to crash. FPM’s own service log is not, by itself, the PHP error log file at issue.
The advisory documents code execution in local tests with both FPM and Apache mod_php under additional assumptions. An unauthenticated remote attacker may be able to execute code, but this does not show that any PHP website can be made to run commands over the internet. Initial access would have the PHP process’s permissions, not necessarily root. PHP rates the flaw Critical, 9.2 on CVSS 4.0. Neither advisory gives a count of compromised servers. PHP advisory for CVE-2026-129496.
Affected versions and the first fixed release for each branch
| PHP | FPM: affected | Date/time: affected | First fixed |
|---|---|---|---|
| 8.2 | 8.2.7–8.2.35 | 8.2.0–8.2.35 | 8.2.36 |
| 8.3 | 8.3.0–8.3.36 | 8.3.0–8.3.36 | 8.3.37 |
| 8.4 | 8.4.0–8.4.27 | 8.4.0–8.4.27 | 8.4.28 |
| 8.5 | 8.5.0–8.5.12 | 8.5.0–8.5.12 | 8.5.13 |
The ranges are inclusive and refer to upstream PHP. You do not have to switch branches to fix these two issues. Debian, Ubuntu and hosting panel vendors can backport fixes without changing the base version. Compare the full package revision with the vendor’s security notice. Official PHP releases.
How to check the PHP runtime serving your site
Two domains on one VPS may run different PHP versions. Check each domain’s handler in the hosting panel, or identify the FPM service or socket receiving requests from NGINX or Apache. For example, for a site using PHP 8.3-FPM on Debian or Ubuntu, these are read-only checks:
Hosting a PHP application?
Compare TERAMONT VPS plans and decide who will maintain the OS, PHP and the services your application needs.


apt-cache policy php8.3-fpm php8.3-common
systemctl status php8.3-fpm --no-pagerThe first command shows the installed and candidate revisions. A match does not prove that a fix is available. The second identifies the service and how long it has been running. Once you have confirmed the vendor’s fixed revision, update the relevant packages and restart the service handling web requests during a maintenance window. For mod_php, restart Apache. For containers, deploy the corrected image to every replica. Then request a dynamic page and check the startup logs.
If your provider has not yet shipped a patch
For FPM: PHP recommends temporarily disabling catch_workers_output in affected pools. Check how you will collect worker messages first. For the timezone issue: resolve startup configuration warnings and restart the master process and its workers. PHP also suggests routing PHP errors to syslog instead of a file. Keep logging enabled and verify that messages arrive. These are separate workarounds; neither replaces the fixed package.
If someone else manages the server, ask: “Which PHP package revision serves this domain, does it include both fixes, and have the processes been restarted?” October’s PHP2Shell fixes do not answer that question. For distribution-specific update procedures, see our guide to updating PHP on a VPS.







