Every site on my maintenance plans gets the PHP security release this week
by Stephen Meehan in Maintenance Services, Server Logs, News
At 14:0 UK time on 19 November 2026, PHP released fixes for every version it still supports. It was the second critical PHP security release in a month, after the one in October.
This release fixes 17 vulnerabilities, and seven of them are rated critical. That is enough for me to want every server I manage updated this week.
Harold's smile or Will Ferrell's tears? Type your website's address into my free Statamic health check to see how many updates it's missed, whether it still gets security updates and which face it earns.
What is the November 2026 PHP security release?
The November 2026 PHP security release is a set of fixed versions of PHP, the programming language that runs on the server behind most websites. WordPress, Drupal and Statamic are all built with it.
PHP publishes updates every four weeks. This one fixes 17 security vulnerabilities across every version PHP still supports, 8.2 to 8.5. The fixed versions are 8.5.13, 8.4.28, 8.3.37 and 8.2.36.
The vulnerabilities are in PHP itself, so a Statamic or Laravel update can't fix them. The update has to happen on the server.
PHP 8.6 came out the same day. It's a new version of the language, not a security fix, and there's no rush to upgrade to it.
PHP 8.5 gets bug fixes until 31 December 2027 and security fixes until 31 December 2029. A site on 8.5 is fully supported for years yet. I'll move sites to 8.6 once I've tested each one on it, as part of the normal updates.
How serious are the PHP vulnerabilities?
The most serious PHP vulnerabilities score 9.2 out of 10 on the Common Vulnerability Scoring System (CVSS). In the worst case, someone could run their own code on a server without logging in.
The PHP security team said the critical ones need "non-default configuration or uncommon setups". Two examples show what that means.
CVE-2026-129289 is in PHP-FPM, the part of PHP that takes each visit from the web server. It could let someone hide a second request inside a visit and run their own code. It only works when the web server keeps its connection to PHP-FPM open between visits. NGINX, the web server on every site I look after, closes that connection by default. CVE stands for Common Vulnerabilities and Exposures, the public list of known security vulnerabilities.
CVE-2026-115560 is one PHP warned about in October and has now fully fixed. It's one of three critical vulnerabilities in PHP's built-in session handling, the way a site remembers a visitor between pages. Laravel, and so Statamic, handles sessions its own way instead.
So a typical Statamic site isn't exposed to the worst of them. Seven critical vulnerabilities is still too many to leave to the monthly update, so I'm not relying on that.
One of the less serious fixes is the easiest to picture. Until this release, PHP could skip encryption when a web address started with a capital HTTPS:// instead of https://. As developer Mattias Geniar pointed out on release day, that meant login tokens, form data and file transfer passwords could travel in plain text. CVE-2026-128064 is rated high rather than critical, and the same update fixes it.
Statamic Watchtower lists every security release for the software a Statamic site runs, in one place. It checks for new releases every hour, and it's free for anyone to use.
Has anyone been attacked through these PHP vulnerabilities?
No attacks had been reported when the fixes came out on 19 November 2026, and I hadn't seen any working attack code published. The details of each vulnerability went public with the fix.
Being affected isn't the same as being hacked. The fix still goes on this week, not next month.
What I'm doing for sites on my maintenance plans
This is one of the critical patches that can't wait for the monthly update. My servers get PHP from the same source Ploi uses, and the fixed versions were out on release day.
Sites on the Max plan come first, because Max includes priority response. I started on those on 19 November. Every site on the Plus and Core plans will be done by Friday 20 November.
For each server, I:
Install the fixed PHP on every production and staging server I look after.
Restart PHP-FPM, so no part of it is left running the old version.
Confirm NGINX closes its connection to PHP-FPM after every visit, the setting the most serious vulnerability needs.
Install any other security updates waiting on the server. If one needs a server restart, I do it at a quiet time or arrange it with the client's IT team.
Check that every site, its Control Panel and its forms work as before.
You don't need to do anything. I'll let you know when your site is done.
What if your site isn't on a maintenance plan?
Ask whoever looks after your server which version of PHP it runs. It needs to be one of the fixed versions above, or anything newer.
PHP 8.1 and older don't get official fixes. Some package maintainers have built their own, but a site that old is overdue a move to a new server.
PHP's security advisories list every vulnerability and the versions it affects.
Keeping PHP up to date is part of every website maintenance plan I offer. Sites on a plan get fixes like this installed and checked without their owners having to ask.
You might also like...
- Patchmageddon and why AI has everyone patching at once
- I built Statamic Watchtower to keep up with security releases
- Every site on my maintenance plans gets the NGINX fix this week
- Darkroom 1.4.0 adds favourites and ends the wait between prompts
- Why the patch gap on your website matters more now
- Plan your Statamic 5 upgrade while it's still supported
- The importance of website maintenance, and what an out-of-date site can cost
- Your Statamic 3 site still works, but it can't be kept secure
- Still on Statamic 4? Updating PHP isn't enough
- PHP2Shell is patched on every site I maintain