Critical PHP Security Update: November's Urgent Flaws
Fixed PHP2Shell in October? That's not enough: PHP just released critical fixes for sessions and PHP-FPM.
by Cleverson Gouvêa

The PHP security update released on November 19, 2026, addresses over 15 vulnerabilities across versions 8.2, 8.3, 8.4, and 8.5, with six of them officially flagged as critical by the project. The most crucial detail for server administrators is this: if you applied the PHP2Shell patch in October, you are still not protected. Today's fixes are separate. Below, I'll explain what has changed, who needs to act quickly, and how to update without taking down your site.
TL;DR
- PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36 were released today, all announced as security releases on php.net.
- Critical vulnerabilities are present in sessions, PHP-FPM, the core, and the Date extension. Several could lead to Remote Code Execution (RCE).
- PHP itself has warned that the 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. Version 8.2 goes out of support on 12/31/2026.
What Today's PHP Security Update Fixes
On Wednesday, November 18, the PHP team published an advance warning: the following day's release would include CRITICAL severity fixes, but critical cases depended on "non-standard configurations or unusual setups." On Thursday, the 19th, all four maintained versions were released simultaneously, each with its official announcement.
The same day also saw the release of PHP 8.6.0, the new major version of the language. 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 path today is 8.3.37, not a jump to 8.6.
Security firm Wiz has dubbed the set of session vulnerabilities phpAfterShell, a nod to October's PHP2Shell. The name is likely to appear in headlines in the coming days, so it's worth knowing that it refers to this release.
A caveat about the numbers: specialized 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. In this post, I use the advisories published by PHP itself on php.net and in the official php-src advisories repository as my basis.
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 the CISA's (the U.S. cybersecurity agency) catalog of exploited vulnerabilities. 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 remember that "the server was updated last month" and cross the item 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 is not a one-time event; it's a routine. This release is the perfect example. One 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 Serious Vulnerabilities, One by One
This table gathers the vulnerabilities that the official PHP repository marks as critical or high, in addition to those most relevant to anyone running a website or LMS 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 termination | Critical |
| CVE-2026-115560 | Sessions | Session serializer 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 living and breathing C:
- Use-after-free occurs when a program continues to use a memory area that has already been freed. An attacker who controls what lands there can, in some cases, divert execution to their own code.
- Request smuggling occurs 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 FPM master process user, which on many servers is root.
Sessions: The Most Sensitive Point
Three of the critical vulnerabilities are in session handling, precisely the part every system with login uses: WordPress, Moodle, Laravel, e-commerce stores. CVE-2026-115560 had a warning since October 23, when PHP recommended disabling session.upload_progress until the full fix was released. The fix arrived today.
PHP-FPM: The Shared Server Risk
The two PHP-FPM vulnerabilities are more concerning for those who share servers. CVE-2026-129291 allows already-executing 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 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 serialization (CVE-2026-129501), and an out-of-bounds read and write in CGI PATH_INFO handling (CVE-2026-129538). Individually, they are less severe, but they show that the release addresses many issues. This is another reason to update the entire version instead of trying to mitigate vulnerability by vulnerability.
Who Needs to Apply the 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 exactly which conditions each CVE requires takes more time than updating. Therefore, I use this priority scale:
Update Today:
- Servers with multiple websites or multiple clients on the same PHP-FPM (shared hosting, reseller, agency hosting clients).
- Applications with file uploads by anonymous users or public forms with sessions.
- Moodle LMS or e-commerce stores with thousands of logged-in users, because 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, without public uploads.
- Internal environments accessible only via VPN.
Can't Wait: those running PHP 8.1 or earlier. There are no official fixes for these versions, neither this time nor in the future. The only solution is to migrate, and I detailed the precautions in the post about updating Moodle's PHP without breaking plugins.
Those on 8.2 should update to 8.2.36 today and immediately schedule the migration to 8.3 or 8.4. Security support for 8.2 ends on 12/31/2026, in six weeks.
How to Apply the PHP Security Update Without Taking Down Your Site
The first step is to know what's actually running. The command-line version isn't always the same as the PHP-FPM version serving your site.
# 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 actually uses, temporarily create a file with <?php phpinfo(); at a URL only you know, check, and then delete it immediately. Leaving phpinfo() public gives any attacker a map of your server.
Update Step-by-Step
- Back up your files and database before any PHP security update in production.
- Check your distribution's package. Debian, Ubuntu, and Red Hat often apply fixes to their own packages (backporting), maintaining a different version number than the official one. In these cases, consult your distribution's security advisory, not just
php -v. - Update in staging first, if you have that environment. Patch releases rarely break compatibility, but older plugins sometimes rely on buggy behavior.
- Restart PHP-FPM, not just Nginx or Apache. Without restarting FPM, old processes continue to run the vulnerable version in memory.
- If you use Docker, rebuild the image with the new tag and recreate the containers. Updating the host does not update the PHP inside the container, as I showed in the post about vulnerable PHP Docker images.
- Test what matters: login, upload, checkout, form submission.
Mitigations for Those Who Can't Update Now
If the update depends on a maintenance window that only opens on the weekend, these measures reduce the attack surface until then:
session.upload_progress.enabled = 0inphp.ini. This is the mitigation PHP itself recommended in October for the session vulnerability. Few systems use this feature, but test first to see 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 offin Nginx) against request smuggling. This has 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 About Maintaining PHP in Production
Two serious security releases in just over a month, and in the same code region. 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 scrutinize 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 on your hosting?" is "I think it's the provider," it's worth reading who applies PHP patches on 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, facing public vulnerabilities with 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 November 10, Outlook had an actively exploited vulnerability with a short fix deadline. Companies with a routine resolved it the same day. The others are still figuring out which machines were affected.
How Agathas Web Addresses This
With managed hosting from Agathas Web, each PHP security update is our responsibility, not the client's. In practice, it works like this:
- Critical patch within 72 hours of public CVE, with this timeframe written into the SLA. Operating system, PHP, database, and critical plugins follow the same routine.
- Update tested in staging before production, in a window agreed upon with you, with backup beforehand and a 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 normal.
- Daily backup, with restore tested monthly. If an update goes wrong, there's a point to revert to.
- Monthly report detailing what was updated and which threats were blocked. You don't need to ask if the server received today's patch.
For educational institutions, Moodle hosting follows the same logic, with the update window coordinated 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 your site runs on, that's the kind of risk worth outsourcing. Contact us and we'll perform 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 corrected packages) resolve them. The actual risk depends on each server's configuration, but updating costs less than investigating case by case.
Action summary: check your PHP-FPM version, back up, update, restart FPM, and test login and upload. If it's PHP 8.1 or earlier, start your migration plan today. And if you prefer this to no longer be your concern, explore managed hosting with included patches.
Related posts

FAA Ground Stop: Was It a Cyberattack? What We Know So Far
The FAA halted every US departure for more than 4 hours. The timeline, the likely cause, whether it was a cyberattack and what's still unknown.

Microsoft Outage: What We Know About the Outlook and Teams Failure
Outlook and Teams have been unstable for more than 20 hours: the timeline, the cause Microsoft admits and what's still unknown.

mod_php vs. PHP-FPM: Risk, Performance, and Migration
PHP identified mod_php as the highest-risk scenario in PHP2Shell. Understand architectural changes and how to migrate to FPM with zero downtime.