Urgent PHP Security Update: November's Critical Vulnerabilities

Did you patch PHP2Shell in October? It's not enough. PHP has released critical fixes for sessions and PHP-FPM today.

by Cleverson Gouvêa

Urgent PHP Security Update: November's Critical Vulnerabilities

The PHP security update on 19 November 2026 addresses over 15 vulnerabilities across versions 8.2, 8.3, 8.4, and 8.5, with six of them officially flagged as critical in the project's advisories. The crucial detail for server administrators is this: those who applied the PHP2Shell patch in October are not protected. Today's fixes are different. Below, I explain what has changed, who needs to act quickly, and how to update without taking your site offline.

TL;DR

  • Today, PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36 were released, all announced as security releases on php.net.
  • Critical vulnerabilities are found in sessions, PHP-FPM, the Core, and the Date extension. Several could lead to Remote Code Execution (RCE).
  • PHP itself warned that critical issues require non-standard configurations or unusual environments. It's urgent, but not a cause for panic.
  • The October patches (CVE-2026-109618 and CVE-2026-109619) do not include these fixes. Servers 'already updated' in October need to be updated again.
  • PHP 8.1 or earlier no longer receives fixes. PHP 8.2 goes out of support on 31/12/2026.

What Today's PHP Security Update Fixes

On Wednesday, 18 November, the PHP team published a pre-notification: the following day's release would include CRITICAL severity fixes, but critical cases depended on "non-standard configurations or unusual setups". On Thursday, 19 November, all four maintained versions were released simultaneously, each with its official announcement.

On the same day, PHP 8.6.0, the new major version of the language, was also released. Its changelog includes the same security fixes, but migrating to a major version is not the path for an emergency. For those on 8.3, the safe route today is 8.3.37, not a jump to 8.6.

Security firm Wiz has named the set of session vulnerabilities phpAfterShell, a nod to October's PHP2Shell. This name is likely to appear in headlines over the coming days, so it's worth knowing it refers to this release.

A caveat regarding the numbers: specialist websites don't agree on the count (17, 18, or "7 critical"), and the CVSS scores of 9.2 circulating come from researchers, not the PHP project itself. In this post, I'm basing my information on the advisories published by PHP on php.net and the official php-src advisories repository.

Why the PHP2Shell Patch Doesn't Replace November's PHP Security Update

In October, PHP2Shell (CVE-2026-109618 and CVE-2026-109619) had confirmed active exploitation and was added to CISA's (the US cybersecurity agency) exploited vulnerabilities catalogue. Many rushed to update to 8.5.12, 8.4.27, and equivalents. They did well. However, these versions do not contain the November fixes.

In practice, this creates a very dangerous false sense of security. A manager might recall that "the server was updated last month" and tick it off their list. If your hosting provider applied the October patch and stopped there, PHP remains vulnerable to the session and FPM flaws fixed today.

Every PHP security update should be part of a routine, not dependent on headlines. I wrote about this trap in the post-PHP2Shell patch management guide: a security patch isn't a one-off event, it's a routine. This release is the perfect example. A month after an emergency fix, another arrives in the same area: sessions.

If you haven't even applied the October update, the situation is worse: your server has actively exploited vulnerabilities and the new ones. The CVE-2026-109618 guide for managers explains that case. The good news is that today's version fixes everything at once.

The Most Critical Vulnerabilities, One by One

This table gathers the vulnerabilities that the official PHP repository marks as critical or high, as well as those most relevant to anyone running a website or VLE in production.

CVE Component Description Severity (Official Advisory)
CVE-2026-126714 Sessions Partially overwritten session file, with possible RCE Critical
CVE-2026-129481 Sessions Use-after-free after interrupted session shutdown Critical
CVE-2026-115560 Sessions Session serialiser conflict, with possible RCE Critical (according to researchers)
CVE-2026-129289 PHP-FPM Request smuggling via unread HTTP body Critical
CVE-2026-129291 PHP-FPM Use-after-free in epoll, local privilege escalation High
CVE-2026-129474 Core Use-after-free in magic method backtraces Critical
CVE-2026-129182 Core Use-after-free in fatal error backtrace after shutdown Critical
CVE-2026-129496 Date Use-after-free in timezone cache Critical

Some terms, for those not fluent in C:

  • Use-after-free is when a program continues to use a memory area that has already been freed. An attacker who controls what ends up there can, in some cases, divert execution to their own code.
  • Request smuggling is when the web server (Nginx, Apache) and PHP-FPM disagree on where an HTTP request ends. The attacker "smuggles" a second request inside the first.
  • Local privilege escalation means that someone already running code with a limited user can elevate to the privileges of the FPM master process, which on many servers is root.

Sessions: The Most Sensitive Point

Three of the critical vulnerabilities are in session handling, precisely the part that every system with a login uses: WordPress, Moodle, Laravel, e-commerce sites. CVE-2026-115560 had already been warned about since 23 October, when PHP recommended disabling the session.upload_progress until a complete fix was released. That fix arrived today.

PHP-FPM: The Risk of Shared Servers

The two PHP-FPM vulnerabilities are of greater concern for those sharing a server. CVE-2026-129291 allows already running code, such as a malicious plugin on one of the sites, to gain the privileges of the master process. In shared hosting, this breaks the barrier between clients. An XSS vulnerability on the FPM status page (CVE-2026-129292) was also fixed, which only matters if that page is exposed.

Other Notable Fixes

There's also an OpenSSL signature verification bypass in Phar archives (CVE-2026-128090), a double free in DOM XML serialisation (CVE-2026-129501), and an out-of-bounds read and write in CGI PATH_INFO handling (CVE-2026-129538). Individually, these are less severe but demonstrate that the release addresses many issues. This provides another reason to update the entire version rather than attempting to mitigate each vulnerability separately.

Who Needs to Apply This PHP Security Update Today

PHP's warning about non-standard configurations is important, but it doesn't make the PHP security update optional. Not every server is exposed to all vulnerabilities. However, figuring out the exact conditions each CVE requires takes more time than simply updating. Therefore, I use this priority scale:

Update today:

  • Servers with multiple websites or clients on the same PHP-FPM (shared hosting, reseller, agency hosting clients).
  • Applications with file uploads by anonymous users or public forms using sessions.
  • Moodle VLEs or e-commerce sites with thousands of logged-in users, as sessions are at the heart of the system.
  • Any server that has not yet received the October patch.

Update this week, with a planned window:

  • Institutional websites without login, on a dedicated server, with no public uploads.
  • Internal environments accessible only via VPN.

Cannot wait: those running PHP 8.1 or earlier. There are no official fixes for these versions, neither this time nor for future updates. The only solution is to migrate, and I've detailed the precautions in the post on updating Moodle's PHP without breaking plugins.

Those on 8.2 should update to 8.2.36 today and immediately schedule migration to 8.3 or 8.4. Security support for 8.2 ends on 31/12/2026, in six weeks' time.

How to Apply the PHP Security Update Without Taking Your Site Offline

The first step is to know what's actually running. The command-line version isn't always the same as the PHP-FPM serving your website.

# Command-line PHP version
php -v

# PHP-FPM version (adjust the number for your environment)
php-fpm8.3 -v

# Session upload progress configuration
php -i | grep session.upload_progress

To confirm what your site is actually using, temporarily create a file with <?php phpinfo(); at a URL only you know, check it, and delete it immediately afterwards. Leaving phpinfo() public hands a server map to any attacker.

Step-by-Step Update Guide

  1. Back up your files and database before any PHP security update in production.
  2. Check your distribution's package. Debian, Ubuntu, and Red Hat often apply fixes to their own packages (backporting), maintaining a different version number from the official one. In these cases, consult your distribution's security advisory, not just php -v.
  3. Update in a staging environment first, if you have one. Patch releases rarely break compatibility, but older plugins sometimes rely on buggy behaviour.
  4. Restart PHP-FPM, not just Nginx or Apache. Without restarting FPM, old processes will continue running the vulnerable version in memory.
  5. If you use Docker, rebuild the image with the new tag and recreate the containers. Updating the host doesn't update the PHP inside the container, as I showed in the post on vulnerable PHP Docker images.
  6. Test what matters: login, upload, checkout, form submission.

Mitigations for Those Unable to Update Immediately

If the update depends on a maintenance window that only opens at the weekend, these measures will reduce the attack surface until then:

  • session.upload_progress.enabled = 0 in php.ini. This is the mitigation PHP itself recommended in October for the session vulnerability. Few systems use this feature, but test beforehand if yours displays an upload progress bar.
  • Block the FPM status page from external access.
  • Review FastCGI keepalive. Wiz researchers suggest disabling connection reuse between the web server and FPM (fastcgi_keep_conn off in Nginx) against request smuggling. This comes with a performance cost, so treat it as a temporary measure.

Mitigation does not replace the PHP security update itself. It buys you a few days, nothing more.

What This Release Teaches Us About Maintaining PHP in Production

Two serious security releases in just over a month, and in the same area of the code. This doesn't indicate that PHP has become less secure, nor that the next PHP security update will be delayed. It indicates that, after a major vulnerability like PHP2Shell, researchers scrutinise the same area and find more. This pattern repeats in almost all popular software.

The lesson for those paying the server bill is about process, not technology:

  • Someone needs to be responsible for knowing when a patch is released. If the answer to "who applies PHP patches to your hosting?" is "I think it's the provider", it's worth reading who applies PHP patches in hosting and confirming in writing.
  • End-of-life versions are a debt with a due date. Those who postponed moving off PHP 8.1 are, as of today, running with public vulnerabilities and no fixes.
  • Inventory prevents surprises. Knowing how many servers, containers, and versions you have is what allows you to update in hours, not weeks.

The same logic applies outside of PHP. On 10 November, Outlook had an actively exploited vulnerability with a short fix deadline. Companies with a routine resolved it the same day. Others are still discovering which machines were affected.

How Agathas Web Addresses This

With Agathas Web's managed hosting, each PHP security update is our responsibility, not the client's. In practice, it works like this:

  • Critical patches within 72 hours of public CVE, with this timeframe stipulated in the SLA. Operating system, PHP, database, and critical plugins follow the same routine.
  • Updates tested in staging before production, within a window agreed with you, with a backup beforehand and controlled PHP-FPM restart.
  • Extra layers while the patch is pending: Cloudflare WAF, fail2ban, operating system hardening, and 24/7 monitoring, with alerts to the technical team when something deviates from the norm.
  • Daily backup, with restore tested monthly. If an update goes wrong, there's a point to revert to.
  • Monthly report detailing what has been updated and which threats were blocked. You won't need to ask if the server received today's patch.

For educational institutions, Moodle hosting follows the same logic, with the update window scheduled not to coincide with exam periods.

If your server is managed by someone with ten other responsibilities, or if you can't currently say which PHP version runs your site, this is the kind of risk worth outsourcing. Contact us for a diagnosis of your current environment.

Conclusion: Update Again, Even If You Updated in October

The PHP security update of November 2026 is not a repeat of PHP2Shell. These are new vulnerabilities in sessions, PHP-FPM, and the core, and only versions 8.5.13, 8.4.28, 8.3.37, and 8.2.36 (or your distribution's patched packages) resolve them. The real risk depends on each server's configuration, but updating costs less than investigating each case individually.

Action summary: check your PHP-FPM version, back up, update, restart FPM, and test login and upload. If you're on PHP 8.1 or earlier, start your migration plan today. And if you'd prefer this to no longer be your concern, explore managed hosting with included patches.