The set of vulnerabilities is dubbed PHP2Shell and disclosure is scheduled for 14:00 UTC with attacks expected to follow soon after.
It is adviced to take offline every non-vital services until the patch has been installed (or the Docker image has been updated with a patched version of PHP)
Update: fix is out https://www.php.net/archive/2026.php#2026-10-21-5
“I felt a great disturbance in the Force, as if millions of Wordpress sites suddenly cried out in terror and were suddenly silenced.”
it’s a lot more than wordpress…
Shouldn’t especially vital services be taken down to secure them?
Yep. Except if taking them down will kill people.
takes down 112 / 911 services
Don’t worry guys, we’re safe now! ꒰ঌ(˶ˆᗜˆ˵)໒꒱
Safe here, we use 999
round these parts we use 0118 999 881 999 119 725 3
0118 999 881 999 119 725 3
We’re YOUR emergency services
I’ll never remember that. I’ll just send an email…
As if those are running anything as recent as php.
For their interactive mapview in the control room they probably do.
Me when I take down only one hundred twelve out of nine hundred eleven services, leaving seven hundred ninety-nine services still running
It’s just one thing after another. I already had to make sure every computer and VPS has the updated CA certificates earlier today. Now I just finished disabling all of my web servers. I hope Debian doesn’t take forever getting the patch out.
They took just a few hours to squeeze out a new ca-certificates. On the other hand the last time there was a huge kernel bug it took well over 24 hours I think…
A bad ca is update a file on every pc and application. A kernal bug is way more involved so it doesn’t make a new problem later.
They took a lot longer than that on some past vulnerabilities, some of them sat unpatched for weeks or months. But it depends on the severity. A remote exploit of severity 9 will probably get expedited.
Spare a moment’s thought for the dev behind the ondrej PHP mirrors.
Could not pull shit from it this morning. I panicked because my distro’s repos did not have the version numbers of the patched packages, but apparently the Ubuntu maintainers back ported the patches. Sigh of relief.
Nextcloud.
Mailcow.
The great hardening continues. Good to see.
The
beatingscyberattacks will continue untilmoralesecurity improves
Think of Louisiana before Katrina. Those systems of pumps and dykes are expensive and had been neglected… which was fine right up until they were severely tested by Katrina.
Our orange city counselman stopped funding repairs and inspections on the dykes and pumps many years ago (when he destroyed CISA). They’ve been deteriorating from neglect ever since.
A large hurricane is going to hit at 14:00 UTC
(In 10 minutes)
It’ll almost certainly be handled quietly and nobody will know but system admins, but this could be a bigger thing than usual.
Synology had a critical system and PHP package update yesterday, could it be related 🤔
No, there is no fix released for this PHP vulnerability
Wouldn’t be surprised if the big guys got first dibs before everyone else
@Guiorgy @shadowtofu That’s not how embargoes work. If “the big guys” release, everybody releases. There have clearly been leaks, but afaik no patches made public yet.
Dibs on the patches? They are not finite.
Commercial patching and the sla’s are huge business. You do know how rhel works right?
Yes. And again, patches aren’t a finite commodity.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters CA (SSL) Certificate Authority Plex Brand of media server package VPS Virtual Private Server (opposed to shared hosting)
3 acronyms in this thread; the most compressed thread commented on today has 19 acronyms.
[Thread #142 for this comm, first seen 21st Oct 2026, 12:40] [FAQ] [Full list] [Contact] [Source code]
laughs in keeping an old archive site still in PHP5
The vulnerabilities go back that far. You’re not safe.
Hey, never said I was laughing out of happiness… 😭
so for the docker images of PHP there currently seems to be no patch? or do you think the RC version includes the fix? Because it was released at 07:00UTC i would think it dosnt yet include the fix. edit: nvm the patched versions without RC are now also in the docker hub repos.
dose anyone know how and where to check if the fix was applied? also do we know if docker hubs Vulnerabilities score already include php2shell CVEs?
I just happened to read this thread after deciding to open Jerboa after months and I stumbled into this, I have been updating my stuff for the past 30’, thank you for making this post and making me aware of this issue! (Even though I’m 8 hours late)
