FREN

Let’s keep in touch

Social

Technology· 10 min read

Critical PHP vulnerabilities of November 2026: what to do now

Seven critical PHP vulnerabilities fixed on 19 November 2026: versions 8.2.36 to 8.5.13, settings to check, interim measures and the checks to carry out.

On 19 November 2026, the PHP project fixed seven critical vulnerabilities, rated 9.2 out of 10, several of which can lead to remote code execution on a server. The fixed versions are PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13. One month after the October vulnerabilities, a server updated on 21 October is vulnerable again. According to PHP, these critical vulnerabilities require a particular setting or setup: this guide explains which ones, how to check yours and how to fix them.

It is aimed at executives, CIOs and application owners whose website or business application runs on PHP: WordPress, PrestaShop, Drupal, Symfony, Laravel or custom development. As in October, the flaws are in PHP itself: it is PHP that has to be updated on the server, not just the application.

What happened

On 18 November 2026, the PHP security team announced security releases for the next day affecting all supported branches, with a highest severity of “critical”. On 19 November, PHP released PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13, with seventeen security advisories, seven of them critical. PHP 8.6.0, released the same day, also includes these fixes. The same day, CERT-FR, the French government CERT, published advisory CERTFR-2026-AVI-1580, which lists eighteen CVEs and recommends applying the fixes.

This release comes shortly after the critical vulnerabilities fixed on 21 October (CVE-2026-109618 and CVE-2026-109619), covered in our October guide. Those are being exploited: the US Cybersecurity and Infrastructure Security Agency (CISA) added them to its catalogue of known exploited vulnerabilities on 26 October, according to the Canadian Centre for Cyber Security. Two of the new vulnerabilities extend the fix for CVE-2026-109619, and a third, CVE-2026-115560, had been flagged by PHP as early as 23 October, with an interim measure.

PHP states that the critical vulnerabilities require “non-default configuration or uncommon setups”. At the time of release, neither PHP nor CERT-FR reported exploitation of these new vulnerabilities. That is no reason not to update: only a check of the configuration actually loaded tells whether a server is exposed, and updating settles the question for every vulnerability at once.

The seven critical vulnerabilities, in plain terms

PHP rates all seven vulnerabilities 9.2 out of 10 (CVSS 4.0). They affect PHP-FPM, session handling, the date extension and the engine. For each one, the last column says what must come together for it to be exploitable.

VulnerabilityComponentAffected branchesExploitation conditions
CVE-2026-129289PHP-FPM8.2 to 8.5A front end that keeps FastCGI connections open (nginx with fastcgi_keep_conn on, Apache with enablereuse=on, HAProxy) and an application that opens php://input without reading it to the end. No authentication required.
CVE-2026-115560Sessions8.2 to 8.5Upload progress tracking enabled, sessions written and read back with two different serialisation formats and, to execute code, exploitable classes in the application.
CVE-2026-126714Sessions (file storage, the default)8.2 to 8.5An interrupted session write, session content influenced by the attacker, exploitable classes in the application.
CVE-2026-129496Date (timezone cache)8.2 to 8.5A warning emitted at PHP startup (for example an invalid date.timezone), an error log written to a file, a non-thread-safe PHP build.
CVE-2026-129474Engine8.5 onlyfatal_error_backtraces enabled (the default in 8.5) and zend.exception_ignore_args disabled, which the production php.ini avoids.
CVE-2026-129182Engine8.5 onlyA fatal error while settings are restored at the end of a request (memory limit, zlib compression), then a subsequent request on the same process. Code execution not demonstrated.
CVE-2026-129481Sessions8.3 to 8.5A fatal error in a callback invoked during session shutdown, then a subsequent request on the same process. Code execution not demonstrated.

Conditions based on PHP’s security advisories published on 19 November 2026.

The most direct vulnerability is the PHP-FPM one (CVE-2026-129289): according to PHP, an unauthenticated attacker can slip a second request into the body of the first and get PHP code executed, with no memory corruption and no race condition. Standard nginx and Apache configurations, which close the FastCGI connection after each request, are not affected by the demonstrated attack. The three session vulnerabilities turn session data into PHP objects: code execution requires the application to contain classes that can be abused. PHP cites demonstrations with Guzzle and Monolog, two very common libraries in PHP projects.

A PHP-FPM vulnerability that leads to root

Among the high-severity vulnerabilities, CVE-2026-129291 (8.8 out of 10) deserves particular attention. It is not attacked from outside: it lets someone who already runs PHP code on the server, through a shared hosting account or a compromised site, gain the privileges of the PHP-FPM master process, which often runs as root. It requires the catch_workers_output option to be enabled in the pool: it is not enabled by default, but PHP states that the official PHP-FPM Docker images enable it. Until the update, PHP recommends disabling it.

Who is affected

BranchVulnerable versionsFixed versionBranch status
PHP 8.5Before 8.5.138.5.13Supported
PHP 8.4Before 8.4.288.4.28Supported
PHP 8.3Before 8.3.378.3.37Security fixes until 31 December 2027
PHP 8.2Before 8.2.368.2.36Security fixes until 31 December 2026
PHP 8.1 and earlierCounted as vulnerable by CERT-FRNo official releaseEnd of life

Versions based on the CERT-FR advisory and PHP’s advisories; branch schedule based on php.net. PHP 8.6.0 includes the fixes.

Fixing it: update, restart, review the configuration

  • Pick up the inventory again. Every server, container and hosting account that runs PHP, with its version and execution mode (PHP-FPM, mod_php, CGI). Public sites, APIs and back offices reachable online first.
  • Install the fixed version through the right channel. Packages from your Linux distribution or the repository you use, a Docker image rebuilt on a fixed base image, or an update by your hosting provider. Some distributions ship the fix without changing the version number: in that case, rely on their security advisory, which lists the CVEs.
  • Restart every PHP process. PHP-FPM, Apache, and long-running processes (FrankenPHP in worker mode, message queue consumers, Laravel Octane). A process started before the update keeps the old version in memory.
  • Review the configuration actually loaded. Upload progress tracking, persistent FastCGI connections, catch_workers_output, startup warnings: these are the settings that determine exposure, today and at the next alert.
  • Check the version being served from the web server, not just on the command line: PHP-FPM and the Apache module can run a different version from the php command.
bash
# Version served by PHP-FPM (adapt the branch number)
php-fpm8.3 -v

# PHP-FPM settings that matter for these vulnerabilities
grep -R "session.upload_progress\|catch_workers_output\|error_log\|date.timezone" /etc/php/8.3/fpm/

# nginx: persistent FastCGI connections?
grep -R "fastcgi_keep_conn" /etc/nginx/

# Apache (mod_proxy_fcgi): connection reuse?
grep -R "enablereuse" /etc/apache2/

If you cannot update straight away

  • Disable upload progress tracking if you do not use it: session.upload_progress.enabled = 0 in every configuration that writes to the same session storage. This reduces exposure to CVE-2026-115560 and CVE-2026-126714.
  • Close FastCGI connections after each request: fastcgi_keep_conn disabled on nginx, enablereuse disabled on Apache, the equivalent setting on other front ends. This is the interim measure for CVE-2026-129289. PHP-FPM must never be exposed directly to an untrusted network.
  • On PHP 8.5: zend.exception_ignore_args = 1 (the production php.ini value) or fatal_error_backtraces = 0. The second setting also covers CVE-2026-129182.
  • Disable catch_workers_output in PHP-FPM pools, against CVE-2026-129291.
  • Remove startup warnings (a valid date.timezone, no obsolete settings) or send PHP errors to syslog rather than to a file, against CVE-2026-129496.
ini
; php.ini (configuration loaded when PHP starts)
session.upload_progress.enabled = 0
zend.exception_ignore_args = 1
date.timezone = Europe/Paris

; PHP-FPM pool (for example /etc/php/8.3/fpm/pool.d/www.conf)
catch_workers_output = no
php_admin_flag[session.upload_progress.enabled] = off

PHP 8.1 and earlier

Branches 8.1 and earlier no longer receive updates from the PHP project. The 19 November advisories do not assess them, and CERT-FR counts every version before 8.2.36 as affected. For these servers, you need a package fixed by your distribution or a long-term support vendor, the interim measures above, and a planned migration. The 8.2 branch itself will no longer receive fixes after 31 December 2026: our guide on the end of support for PHP 8.2 details the migration method.

After the update: check and monitor

  • Every server in the inventory serves PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 or a version fixed by the distribution, checked from the web server.
  • Every PHP process has been restarted, including long-running processes.
  • Upload progress tracking is disabled wherever it is not used, and no explicit setting turns it back on.
  • Front ends do not reuse FastCGI connections, or PHP behind them is up to date.
  • Acceptance environments and old sites have been fixed or taken off the internet.
  • The date of the update and the installed versions are recorded, for your customers or for an audit.

Frequently asked questions

I updated PHP after the October vulnerabilities: am I protected?
No. PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12, released on 21 October, are affected by the vulnerabilities fixed on 19 November. You need PHP 8.2.36, 8.3.37, 8.4.28 or 8.5.13, or a version fixed by your distribution.
Which PHP versions fix the November 2026 vulnerabilities?
PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13, released on 19 November 2026, as well as PHP 8.6.0, released the same day. Branches 8.1 and earlier have no official fixed release.
Are these vulnerabilities exploitable with the default configuration?
For the critical vulnerabilities, PHP says a non-default configuration or an uncommon setup is required: persistent FastCGI connections, upload progress tracking with different session formats, startup warnings, or PHP 8.5 without the production php.ini. Only a review of the configuration actually loaded tells whether your server is exposed; updating settles the question in every case.
My WordPress site is on shared hosting: what should I do?
The hosting provider updates PHP. Check the version in use in your customer area and ask the provider to confirm that the 19 November fixes have been applied. On a shared server, PHP-FPM vulnerability CVE-2026-129291 can let someone running PHP code on the same server gain elevated privileges if the catch_workers_output option is enabled.
Do I need to restart after the update?
Yes, at least the services that run PHP: PHP-FPM, Apache if it uses mod_php, and long-running PHP processes. As long as a process runs with the old version in memory, the vulnerabilities remain exploitable.

Update, then keep the configuration in check

This round of vulnerabilities calls for two steps: update PHP everywhere, then review the handful of settings that determine exposure. The second pays off beyond the emergency: the same settings will come back at the next alert.

If you lack visibility over your PHP servers, or if your applications still run on an end-of-life version, iones’ nearshore team provides web infrastructure security and application maintenance: inventory, updates, configuration review, version migration. Write to us to review your estate.

Sources

  1. Avis CERTFR-2026-AVI-1580 : multiples vulnérabilités dans PHP – CERT-FR (ANSSI), 19 November 2026
  2. PHP: security announcement and versions 8.2.36, 8.3.37, 8.4.28 and 8.5.13 – php.net, announcements of 18 and 19 November 2026
  3. PHP 8 ChangeLog: fixes in version 8.5.13 – php.net, 19 November 2026
  4. Advisory GHSA-qc49-hpvq-g2w6: PHP-FPM request smuggling (CVE-2026-129289) – PHP project, GitHub, 19 November 2026
  5. Advisory GHSA-658j-r8rw-q6mx: session serializer mismatch (CVE-2026-115560) – PHP project, GitHub, 19 November 2026
  6. Advisory GHSA-fm2m-fjf5-v3cp: partially overwritten session files (CVE-2026-126714) – PHP project, GitHub, 19 November 2026
  7. Advisory GHSA-gr4f-wgx5-jpfv: timezone cache use-after-free (CVE-2026-129496) – PHP project, GitHub, 19 November 2026
  8. Advisory GHSA-8mjj-2r7p-4hg2: use-after-free in magic method backtraces (CVE-2026-129474) – PHP project, GitHub, 19 November 2026
  9. Advisory GHSA-2fjv-p558-g82m: last_fatal_error_backtrace use-after-free (CVE-2026-129182) – PHP project, GitHub, 19 November 2026
  10. Advisory GHSA-g3vh-838c-65v7: use-after-free after interrupted session shutdown (CVE-2026-129481) – PHP project, GitHub, 19 November 2026
  11. Advisory GHSA-jm4m-qfqx-967m: PHP-FPM epoll use-after-free (CVE-2026-129291) – PHP project, GitHub, 19 November 2026
  12. PHP Patches Seven Critical RCE Vulnerabilities – SecurityWeek, 19 November 2026
  13. Alert AL26-026: critical vulnerabilities affecting PHP – Canadian Centre for Cyber Security, updates of 23 and 27 October 2026
  14. PHP: Supported Versions (branch schedule) – php.net

Start a project

Ready to take action?

Tell us what you need – we will get back to you quickly with a technical assessment and an action plan.

  • Reply within 48–72 hours
  • No-obligation conversation
  • NDA confidentiality