If your website was patched for PHP2Shell in October, the server it runs on needs a PHP update again. PHP released security fixes for every supported version on Thursday 19 November, and its own advisories say two of them cover cases its October PHP2Shell fix didn’t reach. PHP says neither has been shown to let an attacker run code.
The new versions are PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. PHP calls each one a security release and encourages all users of that branch to upgrade. Across the four, it rates seven of the fixes critical, scoring each 9.2 out of 10 on CVSS v4.0.
We found no reports of any of them being used in attacks when we checked at about 14:15 GMT, and none is on CISA’s list of exploited vulnerabilities.
What PHP fixed
PHP’s changelog lists fixes with CVE numbers for 18 flaws in 8.5.13, 14 in 8.4.28, 13 in 8.3.37 and 12 in 8.2.36. PHP’s advisories say some of the flaws only affect the newer versions.
| Version | Fixes with CVE numbers | Rated critical by PHP |
|---|---|---|
| 8.5.13 | 18 | 7 |
| 8.4.28 | 14 | 5 |
| 8.3.37 | 13 | 5 |
| 8.2.36 | 12 | 4 |
PHP said on 18 November that its critical issues “require either non-default configuration or uncommon setups”. Its advisories, published on GitHub between 14:05 and 14:09 GMT, describe what each one needs. One of the 18 in 8.5.13 is in a library PHP bundles rather than PHP’s own code.
The gaps in the October fix
PHP2Shell was two critical flaws, CVE-2026-109618 and CVE-2026-109619, fixed on 21 October and since used in attacks on firewalls and security gateways. We’ve covered it since.
Two of the new critical fixes go back to the second of those flaws. PHP’s advisory for CVE-2026-129481 calls it “an incomplete fix for CVE-2026-109619”, affecting PHP 8.3 and later. Its advisory for CVE-2026-129182, which only affects 8.5, says “further scenarios have been discovered” after the October fix.
PHP says both can corrupt memory, which could allow code to be run on the server. It says code execution has not been demonstrated for either.
The flaw PHP held back in October
Two days after the PHP2Shell release, PHP warned of “an unlikely RCE vector”, CVE-2026-115560, and said the fix would come in this release. It has.
The advisory says the flaw is in PHP’s session upload progress feature, and that the researchers who reported it ran commands on PHP 8.2 to 8.5 using code from Guzzle and Monolog, two PHP libraries. It needs a particular mix of session settings, session storage shared between sites or processes, and suitable code in the site.
The fix switches upload progress off by default. A server that has the feature switched on explicitly in its configuration keeps it on after the update. PHP’s October advice was to set session.upload_progress.enabled=0 until this release, and a host that did that can leave it in place.
The one that depends on how the server is set up
Another critical fix, for CVE-2026-129289, is in PHP-FPM, a widely used way of running PHP behind nginx or Apache.
PHP says that where the web server keeps its connections to PHP-FPM open between requests, and the site’s code opens the incoming request body without reading all of it, an attacker who isn’t logged in can get their own PHP code run on the server, with no unusual PHP settings needed. It names nginx with fastcgi_keep_conn on and Apache with enablereuse=on among the set-ups affected. Standard nginx and Apache configurations, which close the connection after each request, aren’t affected by the attack PHP describes.
On LiteSpeed’s LSAPI, also used by many hosts, PHP says the same flaw can disrupt requests, but it hasn’t shown it can run code.
Until a server is updated, PHP’s advice is to switch that connection reuse off.
What to do
You can’t fix this from inside WordPress or your website. PHP is updated on the server, so it’s your host’s job, or whoever runs your server.
Linux distributions often patch PHP without changing the version number, so the number your site shows won’t tell you whether today’s fixes are in. Your host can.
Cloudways, the managed host, said at 12:17 GMT, before the release, that it would roll out the patched versions across its platform as soon as they were available. For its Flexible and Autonomous plans, it said, customers have nothing to do and their chosen PHP version won’t change. At 15:24 GMT it said it was rolling out the patched versions across its servers automatically, with each server moved to the latest release of its current PHP version, and that PHP may restart briefly during the update. It said it would post again once patching is complete.
The web host IONOS said at 17:51 GMT that the updates “are being installed on all platforms we operate”, including its Web Hosting and Managed WordPress products, and that customers on those don’t need to do anything. It said customers who run PHP themselves, for example on a VPS or dedicated server, should install the update promptly. It also said it had firewall rules blocking suspicious requests in place before the release, and that its PHP Extended Support covers older PHP versions. Fasthosts posted the same statement, word for word, on its own status page at 18:03 GMT.
If someone else looks after your server, send them this:
PHP released security updates on 19 November (8.5.13, 8.4.28, 8.3.37, 8.2.36), seven of the fixes rated critical, including two that cover cases the October PHP2Shell fix didn’t. When will the server my website runs on have them, either as those versions or as patched packages from your Linux distribution? Does the web server keep its PHP-FPM connections open between requests (fastcgi_keep_conn or enablereuse)? Is session upload progress switched off? I understand that setting doesn’t cover the fixes for the October gaps, so only the update does.
Older versions
PHP 8.1 and older get no fixes from the PHP project, and PHP’s advisory for CVE-2026-115560 says those older versions may also be affected. In WordPress you can see your PHP version under Tools, then Site Health, then Info, then Server.
PHP 8.2 reaches end of life on 31 December 2026, so a site on 8.2 that gets today’s fix still needs to move to a newer version within weeks.
What isn’t known
It isn’t known whether any of these flaws has been used in attacks, or when each host and Linux distribution will have the fixes on its servers.
Changes
Update, 19 November 2026, 18:08 GMT: Added Fasthosts’ 18:03 GMT status update, which repeats IONOS’s statement.
Update, 19 November 2026, 17:53 GMT: Added IONOS’s 17:51 GMT statement that it is installing the updates on all the platforms it operates.
Update, 19 November 2026, 17:35 GMT: Added Cloudways’ 15:24 GMT update saying it had started rolling out the patched PHP versions.
Alex De Sousa is the founder of Digital Royalty, a software development company in Portsmouth that builds websites, web apps and AI tools for UK businesses.