PHP2Shell: The Big Hosts Patched in Hours. Did Your VPS?
By Zachary, Hawthorn Security
Two weeks ago the PHP world had one of its messiest security weeks in years. Two critical remote code execution bugs in PHP itself, a broken embargo, and a scramble to get patches out before attackers caught up.
Most of the big hosting providers handled it well. The bit that worries me is everyone else: the small, self-managed servers that quietly run a huge amount of the UK's business websites.
Here's what happened, and why it matters if you run your own server.
The back story
The bugs, now known as PHP2Shell, are tracked as CVE-2026-109618 and CVE-2026-109619. Both are rated 9.2 out of 10 and allow an attacker to run code on your server without logging in.
This isn't a WordPress plugin or a dodgy Composer package. The flaws are in the PHP runtime itself, triggered through how PHP handles out-of-memory errors and leftover request state. In some setups (Apache with mod_php in particular) the attack can land before your application code even runs. Your code can be perfect and you're still exposed.
The issues were found back in August with the help of AI tooling, and the PHP security team worked quietly on fixes under the usual coordinated disclosure process. Distributions and vendors were told in advance so everyone could ship patches at the same moment.
That was the plan, anyway.
The embargo breaks
On Tuesday 20 October, the CVE numbers started circulating online, along with some inaccurate details (including a 10.0 severity score and wrong release dates). Security researchers picked it up and it spread fast.
The PHP team responded that evening by going public early. They issued an advance warning and pulled the release forward a full day, to Wednesday 21 October at 14:00 UTC (3pm UK time).
It got messier on the Wednesday morning. Chainguard published patched container images more than six hours before the agreed release time. The PHP Foundation later called this out publicly, because once a fix is out in the wild, attackers can compare it with the old code and work out exactly what was broken. Everyone else was still waiting for the official release.
The patches landed as planned: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Because of the severity, the PHP team also published source-only backports for the end-of-life 7.4, 8.0 and 8.1 branches.
Exploitation attempts were seen in the wild from release day, and by 26 October CISA had added CVE-2026-109618 to its Known Exploited Vulnerabilities list.
How the big hosts handled it
Honestly? Pretty well, and mostly by doing the boring thing: installing the standard packages.
- Debian and Ubuntu shipped fixed packages through their normal security repos.
- Ondřej Surý's repository (sury.org), which a lot of Debian and Ubuntu servers use for newer PHP versions, had fixed builds out the same afternoon, all the way back to PHP 5.6.
- cPanel and CloudLinux pushed patched EasyApache and alt-php packages, including backports for older PHP versions.
- Red Hat, AlmaLinux and Rocky followed with their own packages.
By 22 October most major distros and control panels had fixes available. Managed and shared hosts simply ran their usual update pipelines, restarted PHP, and moved on. Customers on decent managed hosting mostly didn't need to lift a finger.
That's the value of a well-run platform: someone is watching, and the update process already exists before the emergency.
The Docker delay
If you run PHP in containers, the picture was a bit different.
The official php images on Docker Hub are built through Docker's own library pipeline, which involves review and multi-step builds. On the day, patched official images didn't appear until roughly two to three hours after php.net published the fix. Projects built on top of the official images (such as the popular serversideup images) waited longer still, with one reporting around four hours between the PHP release and their patched images going live, most of it spent waiting on upstream.
A couple of hours doesn't sound like much, but with an embargo already broken and exploits circulating, it was an uncomfortable gap.
And the bigger catch: a new image on Docker Hub fixes nothing on its own. Your running containers keep the image they started with. Updating the host doesn't touch the PHP inside the container either. You have to rebuild, redeploy, and check what's actually running. Plenty of teams pulled a floating tag, assumed they were safe, and were still serving yesterday's container.
The real problem: small, unmanaged VPSs
This is where I think the real risk sits.
Think of the typical small business setup: a £5 to £20 a month VPS, set up a few years ago by a freelancer or an agency that's since moved on. It runs the website, maybe a booking system or a small Laravel app. Nobody logs into it unless something breaks.
These servers tend to have the same problems:
- No automatic security updates. If nobody runs
apt upgrade, the patch never arrives. - PHP never restarted. Even after updating, PHP-FPM or Apache needs restarting before the fix is actually loaded.
- Old operating systems. Ubuntu 20.04 boxes running PHP 7.4 only get the fix through Ubuntu Pro. Debian 11 doesn't get it from Debian at all. These servers are common, and they're often the ones nobody is looking after.
- Misleading version numbers. On Ubuntu, a patched server still reports the same PHP version (for example 24.04 stays on 8.3.6), so a quick
php -vtells you nothing. People checked, saw the “old” number, and either panicked or assumed it didn't apply to them. - Forgotten servers. Old staging sites, test boxes, that one client site from 2021. If it's on the internet and running PHP, it counts.
It's also not over. A further issue, CVE-2026-115560, involving PHP's session upload progress feature, was disclosed shortly after and at the time of writing still doesn't have a fix. The recommended workaround is to switch off session.upload_progress.enabled. If your server isn't being actively looked after, that change won't happen either.
The big hosts closed the gap within hours. A lot of small VPSs may still be wide open right now, and their owners have no idea.
What you should do
- Find every server and container running PHP. Including the ones you'd forgotten about.
- Check the actual package version, not just
php -v. Compare against your distro's security advisory. - Update and restart PHP. Then confirm the running process is using the patched build.
- Rebuild and redeploy containers. Pulling a new tag isn't enough.
- Apply the session upload progress workaround until PHP ships a fix.
- Check your logs back to around 17 October for anything unusual, especially PHP worker processes spawning shells or other commands.
- Turn on automatic security updates so the next one doesn't rely on someone remembering.
Not sure where you stand?
This is exactly the kind of thing I look at in a Hawthorn Security review. I've spent over 15 years building and running PHP and Laravel applications and the Linux servers they live on, so I know where these setups usually fall down.
A review covers your servers, containers and deployment process, tells you plainly what's exposed and what isn't, and gives you a clear list of fixes in order of priority. No jargon, no scare tactics.
If you've got a VPS that nobody has touched in a while, now is a very good time to find out what's on it.
Book a security review at hawthornsecurity.uk