Security

PHP Security Release, November 2026: Update to 8.5.13, 8.4.28, 8.3.37 or 8.2.36

A watercolor illustration of a florist's long wooden counter with a row of glass vases, where the wilted flowers in several vases have just been replaced with fresh bright blooms and the old stems lie in a neat pile, a visual for the November PHP security release that swaps out flawed code on every supported branch

The November 19 PHP security release fixes critical flaws in every supported branch of PHP. The fixed versions are 8.5.13, 8.4.28, 8.3.37 and 8.2.36. PHP rated the worst issues critical, and several can lead to remote code execution on the right setup.

Every WordPress and Drupal site runs on PHP, and most of our readers rely on a host to install the update. This post covers what was fixed, who is really exposed, where the fixed builds are, and what to do if your host is slow. It is the second critical PHP round in a month, after the PHP2Shell flaws in October. Facts are as of November 20, 2026.

The short version: get every server onto 8.5.13, 8.4.28, 8.3.37 or 8.2.36, then restart PHP-FPM or Apache. cPanel and Plesk shipped the builds on November 19. Debian has fixed packages. Ubuntu was still evaluating as of November 20. If you cannot update today, the stopgaps below close the main attack paths.

What the PHP security release fixes

PHP announced the round a day early. Its November 18 notice on php.net said the highest severity was critical. It also said the critical issues "require either non-default configuration or uncommon setups." On November 19, php.net called each of the four builds "a security release" and urged all users of that branch to upgrade.

The number of fixes depends on the branch. We counted the CVE entries in each branch’s NEWS file in the php-src repository and the PHP 8 ChangeLog.

Branch Fixed version CVEs fixed Security support ends
PHP 8.5 8.5.13 17 December 31, 2029
PHP 8.4 8.4.28 14 December 31, 2028
PHP 8.3 8.3.37 13 December 31, 2027
PHP 8.2 8.2.36 12 December 31, 2026

The support dates come from PHP’s supported versions page. PHP 8.1 and older get no fixes. If a server runs those, the only fix is to move up a branch. If CVE numbers are new to you, start with what a CVE is.

The critical flaws in plain terms

Each fix has a GitHub security advisory from the PHP team. Here are the ones rated critical, with what an attacker needs.

  • Session files can be half overwritten (CVE-2026-126714). The advisory says this hits the files session handler, "which is PHP’s default." An attacker interrupts a session write and leaves a file mixing new and old data. Code execution also needs a usable gadget chain in the app. It scores 9.2 on CVSS v4.

  • Session serializer mismatch (CVE-2026-115560). Per its advisory, session upload progress can write data in one format and read it in another. Code execution again needs a gadget chain. It also scores 9.2.

  • PHP-FPM request smuggling (CVE-2026-129289). The advisory says an unauthenticated attacker can slip a forged FastCGI request into a reused connection. That can run attacker-chosen PHP code. It needs a front end that keeps backend connections open, such as nginx with fastcgi_keep_conn on.

  • Timezone cache use-after-free (CVE-2026-129496). Its advisory says a startup warning written to a PHP error log file leaves a stale pointer. A crafted request to a fresh worker can then crash it or, in demonstrated cases, run code.

  • Magic method backtraces, PHP 8.5 only (CVE-2026-129474). The advisory says the shown attack needs fatal_error_backtraces=1 and zend.exception_ignore_args=0. The stock php.ini-production file sets the second one to 1, which blocks this path.

The release also fixes a PHP-FPM bug that lets code already running in a worker gain the FPM master’s rights, often root (CVE-2026-129291). That one needs catch_workers_output on. The advisory notes that the official PHP-FPM Docker images turn it on. Other fixes cover a Phar signature downgrade, SOAP and DOM memory bugs, and an XSS on the FPM status page.

Who is exposed after the PHP security release

php.net says the critical flaws need non-default or uncommon setups. That is true for most, but not all, of them. Several conditions are common on real WordPress and Drupal servers:

  • Default file sessions. The partial-write bug affects PHP’s default session handler.
  • Error logging to a file. Many hosts log PHP errors to a file. Combined with a startup warning, such as a bad date.timezone value, that is the timezone bug’s trigger.
  • Persistent FastCGI connections. Not the default in nginx or Apache, but some tuned setups turn them on for speed.
  • Docker images. The FPM privilege bug needs a setting the official images enable.

None of the advisories report attacks in the wild as of November 20. The advisories describe demonstrated exploits, though, and the code paths are now public in the fixes. Treat this PHP security release as urgent, even if your setup looks safe.

Stopgaps if you cannot install the PHP security release today

These come from the advisories themselves. They buy time. They do not replace the update.

  1. Turn off session upload progress. Set session.upload_progress.enabled=0 in php.ini or the FPM pool, unless a site needs it. The serializer advisory says calling ini_set() from the application "is too late." The fix itself turns upload progress off by default, so check whether your config turns it back on.

  2. Close FastCGI connections after each request. Leave fastcgi_keep_conn off in nginx and enablereuse off in Apache mod_proxy_fcgi. Never expose a PHP-FPM port to the internet.

  3. Clear startup warnings. Fix bad or deprecated settings that make PHP log warnings at startup, then restart PHP and all workers. Sending PHP errors to syslog also avoids the shown trigger, per the advisory.

  4. On PHP 8.5, set zend.exception_ignore_args=1. Apply it in the config your FPM workers read. The advisory warns that changing only the command-line config is not enough.

  5. Turn off catch_workers_output in FPM pools that do not need it.

  6. For legacy php-cgi setups, set cgi.fix_pathinfo=0 and test your routing. PHP-FPM and Apache mod_php are not affected by that CGI bug, its advisory says.

Our guide to blocking PHP execution in upload folders adds another layer if an attacker gets a file onto the server.

Where to get the PHP security release builds

Most sites get PHP from a host, a control panel or the operating system, not from php.net. Here is what each source showed as of November 20.

Source Status Where we checked
cPanel EasyApache 4 ea-php82, 83, 84 and 85 updated to 8.2.36, 8.3.37, 8.4.28 and 8.5.13 EA4 change log 25.98, November 19
Plesk Obsidian PHP 8.2 to 8.5 updated to the fixed versions Plesk change log, November 19
Debian 13 (trixie) php8.4 8.4.28-1~deb13u1 DSA-6641-1
Debian 12 (bookworm) php8.2 8.2.36-1~deb12u1 DLA-4916-1
Ubuntu 22.04, 24.04, 26.04 Needs evaluation, no notice yet Ubuntu CVE page
Pantheon No November PHP note yet Pantheon release notes

The cPanel entries are in the EasyApache 4 change log. Plesk’s Obsidian change log lists a "PHP Updates" entry on November 19 for all four branches. The Debian versions come from Debian’s security tracker, which still lists testing and unstable as vulnerable.

Ubuntu’s CVE page marks php8.1, php8.3 and php8.5 as "Needs evaluation" and lists no Ubuntu notice. Ubuntu also rates the session flaw Medium priority, lower than its 9.2 score. Ubuntu servers that use a third-party PHP repository get updates from that repository instead. Check which source your server uses.

Like Apache in last week’s Apache HTTP/2 vulnerability, distribution packages often keep an older base number. Check the full package version, not only the PHP version.

How to check a server and a site

To confirm a server has the PHP security release, start with the version. With shell access, php -v shows the command-line PHP version. That may differ from what your web server uses. Check the FPM binary too, for example php-fpm8.4 -v on Debian and Ubuntu. On Debian or Ubuntu, dpkg -l | grep php lists the package versions. These are standard commands, not steps from the advisories.

Without shell access, use the site. In WordPress, Tools, then Site Health, then Info, then Server shows the PHP version. In Drupal, the Status report under Reports shows it. On cPanel, MultiPHP Manager shows each domain’s PHP version.

After any update, restart PHP-FPM or Apache. A package update does not protect a process still running the old code. The timezone advisory also points out that workers inherit state from the parent process, so restart the master, not only reload a pool.

WordPress and Drupal sites

These flaws sit in PHP itself. WordPress, Drupal, plugin and module updates do not fix them. Security plugins that run inside the CMS cannot see most of them.

Some flaws do need help from the application. The session bugs need a gadget chain, and the 8.5 backtrace bug needs request data that reaches a magic method. That makes exposure depend on your plugins, modules and custom code. You cannot audit that quickly across many sites. Patch the server instead.

On shared hosting, one PHP install often serves many sites. A flaw in PHP puts every site on that server at risk. If you manage many client sites on one server, patch that server first. Managed platforms usually patch PHP for you. Our guide to choosing a managed WordPress host covers what to ask about this. Ask in writing which PHP build each site runs and when workers restarted.

PHP 8.2 users and the new PHP 8.6

PHP 8.2.36 is one of the last 8.2 builds. PHP’s supported versions page lists December 31, 2026 as the end of 8.2 security support. Our PHP 8.2 end-of-life guide covers choosing and testing the next version. Our PHP compatibility check walks through testing plugins, themes and custom code.

PHP 8.6.0 also came out on November 19. php.net calls it "a major update to the PHP language," and it carries the same fixes. Do not jump to 8.6 as a quick security fix. Plugins and modules need time to catch up, as our PHP 8.6 preview explains. For this PHP security release, stay on your branch and take the patch.

Updating the package is half the job. Restart PHP-FPM or Apache, then confirm the running version on a test page or in Site Health.

Frequently Asked Questions

What versions does the November PHP security release fix?

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, all released on November 19, 2026. Each one is the fixed build for its branch.

Is the PHP security release critical?

Yes. PHP rated the highest severity critical. It also said the critical issues need non-default configuration or uncommon setups, though some conditions, like file-based sessions, are common.

Are these PHP flaws being exploited?

None of the advisories report attacks in the wild as of November 20, 2026. Several describe working proof-of-concept attacks, so patch now.

Do I need to update PHP 8.1 or older?

PHP 8.1 and older are past end of life and get no fixes from PHP. Move those sites to a supported branch.

Has my host installed the PHP security release?

cPanel and Plesk shipped the builds on November 19, and Debian has fixed packages. Ubuntu was still evaluating on November 20. Ask your host for the exact PHP build and restart time.

What can I do if I cannot update today?

Turn off session upload progress, keep FastCGI connection reuse off, clear PHP startup warnings, and on PHP 8.5 set zend.exception_ignore_args=1. Then update as soon as you can.

Do WordPress or Drupal updates fix these flaws?

No. The flaws are in PHP, not the CMS. Update the PHP build on the server or ask your host to.

Should I upgrade to PHP 8.6 instead?

Not as a quick fix. PHP 8.6.0 is a new major release that needs testing. Take the patch on your current branch first.

Does PHP 8.2.36 extend PHP 8.2 support?

No. PHP 8.2 security support still ends December 31, 2026, per php.net. Plan the move to 8.3 or newer.

Digital Matters

Security Desk