The demo video has been going around Twitter today and apparently the proof of concept is privately being shared around too. The video shows pasting something in the URL and then gaining a shell on the server. It looks completely catastrophic.
I think the best course of action is to just shut your server down before the patch goes live and then bring it back after you have patched.
This is gonna rinse so many LAMP WordPress installs where the PHP version is either not getting a patch or the hosting is managed by the user via a contractor or the hosting is managed by a company with a fleet of custom servers etc etc.
We almost need some bot that logs in to every vulnerable PHP server and turns it off to prevent it being properly exploited before the server admin updates it..
Heh, but for better or for worse, a bunch of people have built businesses out of WordPress and its ecosystem. One of them is my aunt, which is why (as a designated family tech support person, though she does have a part time developer) I'm watching this thread closely!
Does she actually need WordPress/Plugin features or is it mostly about editing the site herself? would something like Publii work too? Static sites dont have CVEs and you still get a nice WYSIWYG editor so she can update the site on her own.
Did this with my parents websites and they are quite happy and I get basically no support calls (and can read threads like this one out of interest only, thankfully)
Sadly yes, it's a whole stack (built for her by a vaguely technical cofounder who has since left the business) with a bunch of business-critical plugins, including Woocommerce for handling credit card payments via Stripe and another plugin handling bookings. It's amazing for what it is but it is a bit of a nightmare to keep going.
Good advice if you're not using the default PHP session settings, but using default settings this means sessions can't be created. At best, that means no-one can log-in. At worst, it completely breaks the site (for those that depend on sessions even for unauthenticated users).
"How to make your site cost unlimited money and have terrible performance". People did this in the Web 1.0 days on occasion and it leads to all kinds of problems for any site with any kind of traffic.
>Or you make an exception for them.
Useless. All you need to do at that point is chain a priv-esc to your existing exploit and you get root.
Paying a ransomware attack tomorrow is very much better, than not having critical medical data for the emergency right now. Of course not having a public facing medical database based on PHP, would be even better, but that might not be a decision that they are able to make right now.
ha! Who knew ignoring critical updates and continuing to run deprecated software while kicking the can down the road while focusing solely on building new features would turn out to be the best security policy after all.
That was how a cluster of Java servers at a former employer avoided the Log4j vulnerability. Though I think they'd be on at least PHP 5 by now (maybe even PHP 7!), so they can't dodge two bullets.
The URL is to show the effects of the exploit. The person's running a python script that runs the exploit and then makes the PHP installation execute an arbitrary shell command. The proof of concept involves writing "pwned" to a publicly accessible location on the web server, then they refresh the browser pointing at the URL to show it's been written.
There are some vulns that warrant a pre-release announcement (in the Drupal community, this happened for a few of the more serious fixes). And prior to the public pre-announcement, there is often informal coordination between some of the larger hosting providers or giant companies who can help roll out the patch more quickly.
Apparently, any PHP server that accepts a POST request is vulnerable to arbitrary code execution on the host (from the FPM user?) with no defense. This is DEFCON 1 of internet security: 70% of all websites are currently vulnerable until 14:00 UTC tomorrow with zero escape hatch other than blocking traffic.
The proof of concept works against any PHP server (5 and up) running in the default configuration, leading directly to RCE without authentication. The PoC out there can be defeated by disabling multi part uploads.
The PoC also requires a known binary to exploit so custom PHP builds may be safe if you're lucky, but this seems to be an extremely bad one.
I applied the mitigation to all my servers when it was released, but now I've stopped all the httpds. A few hours of overnight downtime, vs potentially trying to restore everything from backups tomorrow. Everyone should weigh it up.
I am not affiliated with PHP in any way or sense, I am saying this as someone who is able to see PHP's announcements, and there was no patch or mitigation announced by PHP.
I don't think pulling mitigations from random users online during a developing situation is a good idea. I think shutting down ones PHP services for the time being is a very good idea if that's an option.
If the rumors for these exploits being shared on Twitter are correct this is going to be a nightmare. I wouldn't be surprised if VPS hosts step in to mitigate it somehow since so many cheap/unmaintained LAMP installs are running on those servers.
I don't know if people understand that this actually lowers their reputation, instead of increasing it. Putting so important text as AI slop. Maybe it is not so important, if not worth of modifying themselves.
Yes. Bad themes have been a staple of the Internet ever since it got mainstream, remember <marquee> and <blink>. I'm used to that (although as I said the low contrast is making things extra annoying).
But I'm reading a website for getting information, not LLM fluff.
The exploit is already out. Yeah this looks like it's going to go on history as the worst vulnerability ever. And now with LLMs you'll likely see tens of thousands of agents hacking any php website out there within hours.
Yup, I'm seeing several legit people on X claiming to have seen or found the exploit. Some say that: turning session.upload_progress.enabled off and setting file_uploads = Off will mitigate. But others are claiming that those steps are not enough and "Upload progress can serialize before basic RINT clears BG(serialize)". So, I'm taking no chances and taking my services offline.
I think this exploit + agentic AI (which allows for rapid secret exfiltration/utilization) may be a potent enough combo to trigger a sort of Kessler Syndrome for network security.
To be honest that clueless individual and its pathetically lame security practices made him lose 800 000 Bitcoin belonging to its customers with Mt Gox, which was written in... PHP.
And he went to prison for a few years for it. So he knows something about PHP exploits.
If the problem is in the parser then `file_uploads = Off` doesn't help, PHP still parses the multipart body. That seems to be why they're talking about blocking multipart/form-data on routes that don't take uploads and rate-limiting those that do.
I'm not them, but I'd say Conficker and those other windows file share worms were worse. They went after peoples personal computers rather than web servers so affected people less aware of how to deal with it. It's a little early to tell what this php one will all affect though.
Log4Shell was on a library called Log4J, used by many (but also not that many: Logback is equally as used and wasn't affected by the same vuln). This is straight up php the language.
It depends? I recall being on incident response and checking for that specifically (I worked in a big java shop at the time and was responsible for stuff like this). It was alot of screaming online, but things like Spring Framework used to pull Log4J v1 (ie: not affected) and spring-boot (the modern, way more used one) used Logback (also not affected). You'd get it from like a Kafka/Elastic dependency or similar, but only if you didn't have an SLF4J handler.. like spring would ship Logback for example. Which makes me thing, in general other java shops were mostly not affected as well, given spring is basically the go-to on the java world.
Extremely legacy software wasn't affected either (log4j v1 or apache commons-logging!). Lots of automated scanners flagging the idle jar as well (when the app used Logback for example as the SLF4J implementer, but the scanner saw a transitive for the log4j jar and would scream at you - that's when I stopped caring about github vuln scans btw, it was a shitshow).
Like dont get me wrong, it was a bad vuln, but to me it seems like it was more hype machine and internet screaming than actual vulnerable applications. I do recall Minecraft was vulnerable though, that one was indeed a big target given publicly exposed servers and such.
As a percentage of websites, though, Java is far from ubiquitous. It's probably not even double digit percentages. PHP, meanwhile, is some 70% of websites. So in terms of exploit targets, this is 10x that of Log4J, maybe.
The vulnerability also required you to log arbitrary user provided strings and maybe some other precondition that I can't remember. Nothing at my workplace at the time was affected despite using log4j since user provided data was either parsed (e.g. a uuid) or private/not something we would log.
I got into software dev because of cyber sec, and almost everything I learned revolved around poorly implemented php, so I always stayed away from it when building
There are regular security patches for basically everything these days, including OSs. Why does this notice stand out to you? The post suggests that they're being proactive, and discovered and patched these before they were exploited. Rather they take this transparent approach, as opposed to being silent and/or doing nothing.
This one stands out because it's trivially exploited over the internet on the default configuration for all PHP versions. Most vulnerabilities require being able to run malicious code on the machine or using some rare configuration.
If the rumors going around are true this will be the worst computer security incident in history.
It's not "trivially exploitable". Two or three years ago, this would be a critical issue but require quite some expertise to exploit and exploits definitely wouldn't spread like that. LLMs are shaking the entire security industry.
Yes but that means it is trivially exploitable today since anyone can get access to a LLM and where to point it towards. 2-3 years ago, things were different, that is also correct but that doesn't mean things stay frozen in time.
It's trivially exploitable because it requires no special set up, no special credentials, no privileged access of any kind. If you can call a PHP server and you have the exploit script, you can execute arbitrary code as their `www-data` user.
Usually, attacks are at least conditional and require something that weakens security guarantees.
log4shell was easier to exploit.
It also come with an initial patch that turned out to be incomplete, so everyone had to urgently patch every java web app twice!
Log4Shell required that the attacker be able to generate a log message containing specific parameters. It was a severe exploit, but not one that worked in every Java application with the affected Log4j versions. Attackers had to find calls that logged user submitted text or query paths first. So the list of prerequisites was larger: had to be using Log4j and had to have logging of user generated text.
Still a very large attack surface, but not nearly as ubiquitous as this one.
What an awful video, not only because of the content of many PHP-running sites being exploited, but also because of the awful glitching and vignette effect, an odd dancing anime girl at the bottom and the horrendous music.
I am seeing a lot of words like "unconditional" thrown around but I remind that defense in depth is a thing and you can practice it, or should have been practicing it. You can, for example, disable the `system` function of PHP altogether. You can also arrange for your PHP to be running in a situation where there's no shell, or any other program, to exec. Or for that matter a filesystem.
It's a RCE bug, it does not matter if you disable php functions. It's not arbitrary PHP execution, it's an exploit chain resulting in arbitrary code execution.
What is lower than what? This exploit causes the flow of control to reach zend_call_function with the argument "system". It works at the PHP level and having disabled that function is an absolute defense against the exploit.
It isn't 1998 any more and you can no longer just inject shell code on the heap.
Look, at the end of the day, every major security researcher is going "oh shit" and no amount of tweaks to your configuration is going to limit the blast radius in a way that will actually matter. You're going to need to update PHP, that's the _only_ solution to this problem.
By corrupting memory and causing the CPU to jump from the intended instruction to a different one controlled by the attacker, at which point their instructions control what your process does next. Getting shell does not mean getting it to feed a spicy string to system(), it means tricking something in the process into overwriting memory with bytes that, if read as instructions, tell the CPU to make a system call to spawn a different process running arbitrary code.
You could do that to an internet-connected toaster with a JPEG. The system() function has nothing to do with it.
Indeed, an attacker theoretically can access anything the PHP process has permission to access. However even without limiting permissions (also a good idea) that means the simple/published exploits won't work on your server, and there's a high chance criminals will look for other targets, assuming you're not targeted.
Presumably this makes SELinux enabled distros like fedora are significantly less vulnerable, as the PHP process can only access files in a few contexts?
no idea why this is downvoted. PHP runs typically on linux machines. If you depend on a language feature to prevent 'exploit' and don't utilize the operating systems features to limit access to data.
Shell access is not good, but in many places that wouldn't be the end of the world either.
If your PHP application accesses a database, you've got exfiltration, it doesn't matter in this case. Unless your PHP application is just echoing non sensitive data (i.e. rendering md files)...
For everyone wondering why the patch is not out yet:
There are a handful people responsible for doing a release. They are still asleep.
To be honest, I am also shocked, that the exploit was published that quickly, after the leaked video (which was the reason, why the announcement happened in the first place, at that specific time). We expected a bit more time, even with LLMs...
This is something of a fallacy. "The Industry" cannot learn.
But laws and regulations can require better security.
As in the history of seatbelts in vehicles, tech tool stacks are insecure by design and no one is ever really held accountable... until the cost is deemed too high.
It's evident that we have not reached that limit yet.
How? Biggest organisations and shared hosting providers had a chance to patch and protect their users. Everyone else will learn about the vulnerability the second patch comes out (this is also fixable with a configuration chance, so nobody needs to wait for their distro). This was the right approach and it worked.
The problem is that, since proofs-of-concept have leaked but the patch isn't available, bad guys can attack any site whose operators aren't part of the club, and the only thing the operators can really do to prevent that is to take the site offline. (PHP core team has denied that the configuration change fixes the problem.) I would call this a significantly worse outcome than everyone finding out about the vulnerability at the same time, since in that case operators can take timely action if they get the news quickly enough.
People here tend to be part of the silicon Valley insider club that gets access to all the cool offensive models, the expensive licensed software and services and insider information under NDA
They didn't release the patch out of fear that someone would quickly use the patch to develop an exploit, meaning an exploit is available shortly after the patch.
What they have achieved by delaying the patch is that exploits are now available publicly before a patch.
Also they could’ve sent patches to at least some trusted members/maintainers/distros/hyperscalers/big Hosters/plesk/cpanel.
It would’ve been easier to make some kind of coordinated release.
We've been working with the team on the coordinated disclosure, but I made the call to get these out early when exploits hit in the wild.
The vulnerability and patch are both very complex, and the maintainers did an incredible job on this one. We tested the patch extensively and it's holding up well.
We've made these images free and will keep them that way.
What an incredible irresponsible move essentially 0-daying everyone who was working toward coordinated disclosure to ensure everyone had images or distro packages to update to.
what possible reading of "I made the call to get these out early when exploits hit in the wild" contorts into "these exploits hit in the wild after i made the call to get these out early" with flipped causality?
sure, i'm happy to recant my rather tepid defense of chainguard in the case that what was said upthread was a blatant fabrication. i'm even open to being convinced that it was.
as it stands though, what i replied to wasn't a useful addition to the discussion. it could easily become so by either being made contingent upon the possibility of that being a lie, or being bundled with an assertion like yours that chainguard is not to be taken at their word. doing neither and simply responding as if a causally opposite statement had been made is just a non sequitur.
Publishing a patch beforehand potentially multiplies the impact. Now the actual bug(s) can be diffed from the source. Whereas existing PoCs (after verifying whether it even works), obfuscated at least a bit about the details. It is not so clear what is the best approach.
Yesterday the actual bugs plus many more (though less critical) were discovered by the people pointing their LLMs at it. I am confident no new bugs will be found by looking at binary diffs compared to what was already surfaced.
If you want to 'adopt' a new reality, you talk to all parties, and everyone moves up the release. That's how agreements and trust work. If you don't do so? No one will trust you ever again.
Yes but they obtained this information based on the one-sided courtesy of another party, under a scheme that tried to get as many people to safeguard together.
If the first party to receive this information says, "Wow, of course I must act on this, because customers are on the line," then it makes sense to simply choose who you tell more carefully or not at all.
I find it really interesting how no one has been able to produce a POC after the blogs hit the public. Something key was probably omitted from the disclosure to prevent exactly this.
"We took our website down this morning when the "PoC"s were released, only serving a static website. Our customers were not pleased. Then we got contacted by Chainguard affiliates using our public support form if we would like to schedule a meeting with them, so that they could sell us their security services."
This is nonsense, disappointed to see that publicly from a core dev. Yes, some people are asleep, but the decision was made to wait, to ensure the patch is only made available when users are actually able to install the update and we're giving distros the time to build PHP packages.
Honestly, kindarails2shell resulted in a responsible disclosure coordination followed by the decision to release early since it was reversed too quickly. Even just a hint of a 0-day is enough to cause people to look for it and exploit it with LLMs.
That's horribly naive with an installed base this size and if you are that geographically dependent then I would hope to read how this will be dealt with going forward.
Can you please explain what you mean rather than asking questions like this?
I think you are assuming I am running PHP which I haven't used in production for more than a decade. That doesn't change the fact that if you power this many websites that you should have a plan in place for when there is a critical issue.
I am used to Python. Hard to switch to something else until I am forced to. I am trying to manage agentic coding at least to the point where I can identify bugs with my own eyes instead of purely believing the LLMs. I know I will cheat and let an LLM take over the entire Rust app if I tried.
NodeJS and Java are in a similar place (this CVE is a memory safety issue in PHP's C-language interpreter) but Go's compiler/runtime is written in Go and is memory-safe all the way down to the assembly.
Much of Node’s standard library is written in JavaScript, which can’t go on to exploit V8 vulnerabilities even given similar types of bugs, so I wouldn’t say it’s in a similar place. Not as familiar with Java, but I expect PHP is in a class of its own here.
How can I try this to see if I should shut things down myself. I run a 6 figure stealth and have a day job for fintech in 9 figures all php so kinda worried
But created my own based on it since it feels sketchy running someone else's exploit poc ya know. Ran it first in a vm before running it against a production site.
Facebook hasn't used PHP for a very long time. It's been using Hack for over 12 years, which was initially based off PHP but it's deviated quite significantly now. It's now nearly entirely statically-typed, and has a bunch of features that PHP doesn't have. IO is fully asynchronous using async/await syntax (like C# or JavaScript), functions can be marked as pure, and a bunch of other things useful in large codebases.
It still uses the same request model as PHP, since that's genuinely useful for web requests. It's easier to avoid memory leaks if each request is entirely self-contained and there's no global state persisted between requests (other than APC and opcode caches)
This link gets me a shitton of extremely intrusiv ads, some of which look like malware (auto-downloading an "OperaSetup.exe"). Is pastebin already compromised?
Meh, I'll just roll PROD back to our 4.7 image, then head down to the pub for a pint until this all blows over... Only 3 years of data will be missing... No biggie! LOL :P
Years ago I migrated all my personal sites to being statically generated, since they don't have actual dynamic content anyway. That was a good decision.
Same here. And for the dynamic content, I host dedicated, small services, or client side code.
Not only 10 years of no more security updates. But hosting static content is cheap, performant and sustainable. Bot literally (you can move the content anywhere, using any kind of server) and in energy sense.
While I understand it is not for everyone to write markdown files and run build commands, I strongly urge anyone with a WordPress or drupal site to give the various jamstacks, or static site builders and guis a test run.
Only 53 comments for what's most likely going to be the biggest vulnerability in history? I don't understand how this isn't getting more attention. The exploit is already out and it's basically shell access on any php website out there.
It's also very early in EU and evening/night time in part of US. The information that was out earlier was on level "make sure you update tomorrow when the patch comes out", the actual details weren't out yet.
Off-topic but Reddit now requires sign-in to see old.reddit. They destroyed it, "to keep us safe".
Further more, if in Australia or a few other places like Brazil, UK, France, reddit won't let you sign in at all unless you're proven to be over 16. Bottom line, linking to old.reddit is similar to linking to a paywalled article.
They degraded old.reddit even for logged in users - images show as <image>and when you click the link you are redirected to new reddit layout just to see the picture
Once the dust has settled, it would be interesting to give LLMs the pre-patch source code and see whether any of them can identify this chain of vulnerabilities. Even if they can't identify the full chain, can they at least spot one of the constituent bugs and recognise its seriousness?
The original exploit, and then when the rumors of a big critical patch got out, the people who are leaking the details online probably used an LLM to find the exploit again.
Just revealing that an unpatched exploit exists in $XYZ these days basically guarantees that a bunch of people are going to target $XYZ with LLMs looking for that exploit.
I would have expected there to be a hundred entities running every single model over major code like PHP, and clang, and pretty much any behemoth open source project the world relies on. This is the sort of thing the model makers should be doing as a matter of course, as part of routine testing of their new models.
> I would have expected there to be a hundred entities running every single model over major code like PHP, and clang, and pretty much any behemoth open source project the world relies on. This is the sort of thing the model makers should be doing as a matter of course, when they’re testing their new models.
Well, that would be super nice of them.
From a Machiavellian standpoint it may benefit the people with the most powerful models to let some serious RCEs like this PHP one get widely exploited in damaging ways to further their regulatory capture argument that open weight models have to be legally banned and only locked down models with enforced guardrails around usage can be allowed.
From a marketing standpoint, having the first model to find a bug of this magnitude and severity would be a pretty damn impressive proof of capability. Finding previously unknown, critical vulnerabilities in widely used open-source software could become a gold-standard test of frontier AI competence.
Exactly. I thought this is exactly what Anthropic's Project Glasswing was meant to be, and targeted at critical internet infrastructure.
Either Mythos is useless and didn't find this (hint: Opus 5.5 will find this once it knows where to look)... or, they did find it, and this is one of many vulnerabilities they're covering up via "guardrails".
I'll be a lot happier if I wake up tomorrow and find this was found with help from Anthropic (or even OpenAI) but I won't hold my breath.
A PHP core dev suggested all the mitigations getting posted are not enough and that if possible you need to shut down any PHP app until the patch comes out https://phpc.social/@Girgias/117476510850918355
Just as a scripting language on my own laptop, nothing prod. But one thing I notice, even coming back to it after a little while, even after using Python for everything, I find I am effortlessly productive with it.
There was an article I read recently about a blind developer who finds it easy to write in, as the "$" for the variable names makes it easier for him to identify what's going on in any given line of code.
Like any language it has advantages and disadvantages.
Writers/editors really, really like Wordpress for some reason, which is like 40% of the Internet, add to that all the other Php stuff. At $DAY_JOB we have a Wordpress instance behind our VPN and use the json API to send the articles to a front-end server written in something else. Forces us to duplicate some of the front-end plugin code (and we try to not use many) but we get peace of mind in exchange.
I think the ubiquiti edgerouter admin interfaces use PHP. I don’t know about mikrotik, but wouldn’t surprise me if there are a lot of those devices hanging off the internet on some nonstandard port.
Unsure what the correct response from the PHP team is here - I hope there's been plenty of work done behind the scenes to mitigate this on unpatched servers because there's not a chance defenders win the race everywhere it matters once the patches are out.
If you put the oauth wall in front of the application before it can even reach PHP (i.e. in your nginx/caddy/apache config), then no, assuming all paths are covered.
If the oauth wall is managed by PHP, then it looks like the answer is yes, you’re vulnerable to client connections that haven’t logged in.
This looks like a bug in PHP’s assembly of multipart responses & you can feed one of those to the PHP backend with a simple web request, no auth required I think.
Rather than taking your site down tonight, if you have cloudflare handling your DNS, orangeclouding your domain, you can use its free security rules to just block all post requests until tomorrow rather than taking your whole site offline. Drop this into a rule: `http.request.method in {"POST" "PUT" "PATCH" "DELETE"}`
Of course you can do this with web server (eg Apache) config as well, but the CF rule is something you can do now on your phone.
I’m not saying I know this works as a mitigation, but it seems like it could at least contribute to a temporary guard until you get patch in place. Everything I’ve seen about the exploits seem to revolve around multipart form submissions.
Haha you’re right, but the skill you need to be good with is probably eye strain tolerance. But must needs and all. :) If you don’t use a WAF of some type, the risk is probably sufficient to warrant firing up the laptop tonight or worst case use the phone.
Don’t forget to firewall your webserver so it will only accept traffic that actually went through Cloudflare. This is the most false sense of security one can get.
I help manage a few sites hosted on WPEngine, and taking them down is not an easy call to make. After making sure that our environments had the latest everything (WordPress version, PHP version, all plugins and themes on the latest), I contacted WPEngine support briefly.
They're on top of it as I would expect any major PHP hosting service to be. After asking if there was anything I could do to prep for php2shell (seemingly not), I just pleaded to be first in line when they apply patches and let them go.
How are others in similar situations handling this?
The exploits seem to rely on multipart form submissions. In a normal setup, I don’t believe PHP’s multipart parser processes GET requests.
Therefore, a temp mitigation that runs short of shutting your site down is to temporarily block POST requests until you can get the patches in place. This will screw up any form functionality, including your WP login form, but keeps your site presence up. A failed form submission is probably a better look than no site presence. You can affect this with Apache config or by using a WAF. For instance if you have cloudflare caching your domain, use a free security rule to block all POST requests until your patches are in. Something like `http.request.method in {"POST" "PUT" "PATCH" "DELETE"}`
Also, unless your server is specifically set up to only accept requests from Cloudflare, someone could likely send a request directly to your IP, so you might consider blocking multipart requests at the server level. For Nginx I added the following to all /server blocks:
if ($http_content_type ~* "multipart") { return 403; }
Luckily our service doesn't use multipart for any critical requests.
So, theoretically, if you wanted to hack a server but you don't know what OS/PHP, version they're running, you could compile a list of every delta for every litespeed release and then bruteforce it, right?
Not necessarily. Most apps should build in reproducible way these days. That means you can compile the same versions and likely get the same offsets. (+/- custom options applied to your local system)
Well, PHP has an insane number of compilation flags, so the chances of your build being the same as $GENERIC_PLATFORM's is not as high as you think.
So, if the offsets were in fact different, would the explots still work? (I think the answer is actually yes based on what I read/saw; I think the PoC dynamically calculates these offsets? Not 100% sure, but we shouldn't take chances.)
PHP as it is desperately needed the speedups in the 7 and 8 series releases to be relevant, performance loss of that magnitude is simply not going to be accepted anywhere
I'm a sysadmin that manages several servers, I realized I was vulnerable and reproduced what I found on our systems, it appears that simply disabling progress with php_admin_flag session.upload_progress.enabled Off renders the exploit inert...
If you use Nginx, you can temporarly block the subject by disallowing multipart sendings to PHP. This is quite a problem for a lot of forms, but way better that being hacked.
Here is an Nginx patch :
if ($http_content_type ~* "multipart") {
return 403;
}
You can also turn of session progress in php.ini as mentionned but that does not seem to cover every cases :
session.upload_progress.enabled = Off
Have you tested this against a POC to see if it actually mitigates? Seeing a lot of proposed mitigations but with very little detail about whether they worked or not.
It assumes PHP frees the upload progress data when it reloads the session. But PHP 8.4 (the one we use is 8.4.24, i don't know for other versions) calls Z_TRY_ADDREF(progress->data) to keep that data alive. The fake function call also seems to contain invalid fields.
This makes me question this particular PoC, not the official PHP security warning. I have not reproduced the exploit, so this is a concern based on reading the code, not proof that the real vulnerabilities cannot be exploited.
But anyway the CVE still exists, and the exploitation is tied to multipart, disabling it seems the best thing you can do now without shutting everything down.
I have tried the so-called-POC of the URL you linked, it seems it is not a full POC. I have tested it against my local PHP instances; it does not work.
God damn Claude (Opus, Fable, either) is not even helping because of their god damn shitty safeguards. Thank you, Anthropic, for letting bad guys win. I can't tell you how much I want open-weight models to work at home that can handle this type of work in the future without bullshitting about safeguards.
these safeguards are insane. codex would do some fix, them say "hm, my change has introduced a vulnerability. let me write a test for it and then do the fix" and the safeguard stops it.
I hope that people will realize that PHP is unsuited for public websites and that they need to switch to secure technologies like Java, ASP.NET or Rust.
PHP contains an almost endless stream of vulnerabilities since its inception almost 3 decades ago. Proponents claim that it's getting better but this just goes to show that nothing's changed.
Wow, that's a terrible one. Shut down old apps (that I'd forked and upgraded to latest) I had that were PHP. Sadly, my blog was on Mediawiki and so I've got to turn that off too. Tomorrow we learn.
EDIT: Ha, Claude just took the blog and rendered all pages and now it is a static site! I'll restore the Mediawiki once I can fix the issue.
> WP Engine Security and Engineering have enabled WAF rules for all customers using GES and AN. Mitigations are currently being deployed across the rest of our infrastructure, and official patches will be applied as soon as they become available.
We observed this update ourselves and suspected it to be a mitigation when it was rolled, but I can't find any definitive record that these rules are about the PHP vulnerability. Do you have more info?
<p>Due to an <a href="https://www.php.net/archive/2026.php#2026-10-20-1">upcoming significant vulnerability disclosure</a> with no official mitigation, services are currently offline as a precaution. Services will not be restored until at least later in the day on October 21. This time may also be spent on additional maintenance, so this message may be periodically unavailable.</p>
> The OpenStreetMap.org operations team have decided to temporarily shutdown a number of key secondary OSM.org services due to a critical PHP security vulnerability.
That rumor is false, probably because Calif, the firm that discovered the exploit also just published an OpenBSD ASLR bypass people think they must be connected.
Php2shell is completely language level. By the time the OS sees it it's just a function of the webserver.
It is other way around, it was a top post, but AFAIK anti flamewar measures kick in when there are many comments compared to up votes. I mean it isn't bad heuristics when discussion already shifts in "PHP bad" direction.
That's not likely to happen. You don't even know what the exploit is.
Anyway my point is I'm much less likely to get hacked in this new era of AI assistance, as I'm only a few days behind, rathe than a few months or years behind.
> I'm much less likely to get hacked in this new era of AI assistance, as I'm only a few days behind, rathe than a few months or years behind.
Yes, but also, attackers are much faster now and complex chains of vulnerabilities became much easier to carry out. In the past, you might have just been "secure" because nobody cared to put in the time to target you unless you were unlucky. Now, many people have the capability and can completely automatize it.
We essentially had security through obscurity for a long time. It was always dangerous. It's good that it ends. But the transition might be rough.
True, it's a theory; basically a hypothesis derived from my experience with LLMs and their performance in CTFs/finding and exploiting vulnerabilities. Plausible, I believe, but I don't have any hard evidence of it happening.
Maybe the effort and required hardware of running an LLM locally have so far prevented widespread exploitation? Maybe open-weight LLMs are too far behind at the moment? Maybe it's happening but we didn't notice it for some reason?
I would strongly assume that it will happen at some point if it isn't already.
if is happening already, there would be stats to back it up. My brief 5 minutes of research suggests it is not.
in my experience AI is helping me defend against potential vulnerabilities, and so the net impact of these threats is net zero or less, even if I'm quite slow in patching stuff
> Anyway my point is I'm much less likely to get hacked in this new era of AI assistance, as I'm only a few days behind, rathe than a few months or years behind.
Your agent can't help you before the patch is rolled out, so let's not lose sight that the fix to this vulnerability will be:
apt update && apt upgrade
If you didn't know how to keep your server up to date before agents, then perhaps a managed hosting service would be a better fit?
The reason we (used to) have responsible disclosure timelines is so that the information & software to fix vulnerabilities can be assessed, organised, written up. Builds could get built, attackers and defenders find out at once. But crucially, defenders could use the normal channels to fix their installations and be sure they'd covered themselves.
When a PoC drops before that timeline is up (like now!) the attackers get a head start because they have less work to do - just figure out how to use it to their payload, start spraying it out.
Meanwhile maintainers don't want release an incomplete or misunderstood fix. Otherwise they'd risk people updating and believing that they're safe when they're not. Even a fragment of misinformation from an official channel will spread like wildfire. So when you demand fixes NOW you're demanding something that may not be completely understood.
So (I'm sure we'll find out but) I believe this 2pm timeline was already as soon as is human possible for the PHP team to do a repsonsible job, and not risk us having to come back tomorrow for a fix to the fix.
LLMs gives attackers the advantage for a while, and it means we'll have to tighten the secrecy around even the rumour of a vulnerability.
Humans generally have the need for a process called "sleep" where people are generally required to go horizontal and unconscious for at least 6 hours per day.
No, ‘responsible disclosure’ was and always has been a response from vendors not patching their software or building secure software to start with, and trying to frame researchers as responsible for their shoddy work.
As far as I can tell, there is no proper mitigation beyond patching. Unless we count turning off your service as a mitigation. Cloudflare is currently busy playing whack-a-mole with new vectors so it’s probably not feasible to properly mitigate it on the edge either.
Improper mitigation is still better than literally nothing - a simple "this may not cover everything, but block POST at the edge might help" can go a long way.
Mindboggling, wtf don't they release it if its ready and exploit is in the wild, its a lot of time until 14:00 UTC and a lot of websites will be breached.
They should have shut up, released a new stealth PHP version and told everyone to update ASAP. They gave way to many details ahead allowing some AI agents to find the vulnerability within half an hour...
The update was withheld because releasing it without notifying major providers and distros would turn it into the same race, with ai having a release is the same thing as a disclosure.
This would've worked if other people were able to shut up about it. Because its existence got leaked they posted the announcement
There is no functional difference between doing just an announcement and doing an announcement with a series of builds containing the patch while withholding the source code. You do understand that right?
A message as vague as "there is a major RCE somewhere in this entire programming language" is usually pretty safe. We'll see how the details actually got out in this situation and whether the announcement caused it, but it still took a while. If you put out a patched build people will find and decompile the changes nearly instantly.
Yep. It's probably one of a handful of functions. It'll be based on request input, a script doesn't have to call the function, and it works with default configuration. I bet it takes a half hour for AI to figure it out.
Php4 -> 5 was a massive change including zendengine2 and an overhaul of many modules. Fortunately that information really doesn't tell us much. (Also it was a year of work between the first beta and the release - many changes at that time)
I mean an agent can walk those changes, but it's close to just walking all the whole source / research from scratch at that point.
One security provider put "session.upload_progress.enabled, session.use_strict_mode" in the SEO keywords for their initial announcement, which was probably a good enough clue to feed to an LLM. https://web.archive.org/web/20261021005246/https://sansec.io... (go to page source, search for session.upload_progress). At least one person on Twitter saw this: https://x.com/its5q/status/2112700519261032497 Of course there's enough people who knew about this that the exploit vector may have leaked out to the general public through a different source as well.
A patched build is strictly more information, and you'd only need to cross correlate between the two.
At this point shipping the build already may have been the best option but not necessarily everyone is actually able to ship yet. And this is of course assuming the actual vulnerability is the same one as the PoCs that are being tried, and not something even nastier instead
I'm keeping a list [1] of all the (possible) precautions one can take, ahead of the patches appearing in a few hours. Exploits are now circulating, according to Cloudflare's CTO, so _any_ mitigation is worth investigating
Given that this affects every PHP version from the past decade, and that the exploit instructions are circulating at the top of twitter, and that there's no fix available yet, it doesn't seem outrageous to assume every major PHP website is already compromised?
The upgrade instructions here should include torching your hosts and starting again.
Sure, im referring to systems being turned off even if they are not running PHP at all. Out of fear of spillover effects or because they are unsure what they are running.
It’s probably advisable to go through your password manager and start deleting any accounts you no longer use. And of course make sure that you have zero shared passwords
I would assume that in many (smaller, non-professional) systems/code bases, it is also possible to poison the backups and code base in general. This would have been a major effort in the pre-LLM age, but it should be pretty easy now. As soon as such instructions are out there, people (or rather LLMs) are going to find ways to make the threat persist.
People love hating on PHP. But Go has CVEs like every week, and people are getting tired of updating it. I don't think there is a fundamental "PHP bad" argument beyond just "hating on it". While Go/Node have grown much more than PHP, PHP is definitely alive.
> Rust is literally the best positioned language to handle the upcoming onslaught of CVEs.
Rust is also a language with no real stdlib, and so you have to import crates for everything including the kitchen sink.
Which opens you up to the very real risk of supply chain vulnerabilities unless you make an active effort to code review your imports and keep the length of your import list under control.[1][2][3]
Rust supporters also need to urgently realise that memory safe != secure. It is very much possible to have vulnerabilities in memory safe code.
This has been demonstrated by Cloudflare[4] and countless others.
Age-old vulnerability classes such as input validation, error handling and many others are still very much possible in a Rust codebase.
So please. Yes, I'm sure Rust is a fantastic memory-safe language. But do not portray it as being magically immune from CVEs.
If you "really" want to secure the web you reduce the blast radius - there's absolutely no reason that most websites (99% static) are served live from CGI_BIN.
Well-architected solutions would have the static part broken out so only the dynamic content is on a separate domain/host and that part can be secured as needed. Then something like this only turns off your forms/upload dialogs.
I'm not rising to that bait. I'm sure you know perfectly well what I mean.
So let's just be polite, cordial and leave that topic there there. I'm sure you know its a topic that attracts 'strong views', particularly from the Rust side, which is no doubt why you're trying to engage on it.
The only times I had to use third party packages for basic stuff, was when developing embedded software on limited hardware.
Do you mean that for async we need third party runtimes like tokyo? Or that types and utilities that many other languages ship by default in stdlib, like http aren't in rusts?
I'm sorry for the tone of my post. It was meant as honest surprise, but I clearly see now how it sounds baity and provoking.
Not who you’re replying to, but Rust lacks things I assumed were basics in any modern language, like random number generation, JSON handling, and regex. I understood the reasoning once I looked into why, but it was still startling at first.
In contrast (I know this is apples to oranges), Python’s stdlib is incredibly broad. colorsys lets you convert between color spaces. plistlib lets you read and write Apple’s property list files. graphlib has a topological sorter, which can lead to hilariously short interview questions when the interviewer isn’t familiar with Python’s stdlib.
I think the actual difference is that for Go there is likely a build pipeline set up, while for PHP most people can't even touch the binary, because they have a shared hoster. I would sure love to be able to just recompile PHP right now.
govulncheck tells me if my codebase is actually affected by CVEs or not. So if there's 50 CVE'd modules but my codebase doesn't use them, I sleep.
Secondly, the fix is almost always "go get -u <affected module>", and because it's a CVE, it's usually just a bugfix release and still completely compatible with how I'm using it... but I run the test suite to be more certain.
Not the one you are replying to, but an argument I heard is that
1) It is now much easier to work in a language with better security features such as Rust. Previously, there definitely was some kind of trade-off between accessibility, performance, and security, and some people argue that this is over. I don't know if this is true, but it seems plausible.
2) You can now translate your legacy projects to a different language much more easily. This is definitely true, but that doesn't mean it doesn't introduce new/other problems or that it is easy enough (again, I simply don't know).
2 makes sense. 1 is immensely scary as an argument.
If you don't understand the language(eg, not easy to work with), don't work professionally in it. All LLM work need audit, a second set of eyes, just as work from a coworker needs peer review prior to sign off.
How can one peer review an LLM without full, experienced knowledge?
The conversation should be about having more variety in structural components, not less: if you kill php and everyone starts using Go for example, the next CVE found in Go will impact as much. The real way is to have more widespread ecosystems.
I don't want to jinx it but... A discussion about, of all languages out there, PHP being the one hit by that and not, say, Go or Java or Rust or Haskell etc.?
Can we discuss that at least a tiny bit?
How do people feel about running servers with PHP today?
I mean no language is immune to issues. Java world constantly sees fixes for both JVM and libraries. For example, besides famous log4shell, you can see still see in HTTP access log that bots are checking for vulnerable Struts versions. On the other hand, Java pushed to 100% Java (no native code) database drivers, while PHP strongly relies on c/c++ extensions, cause PHP is/was too slow.
If there is any other difference, I think it just comes to legacy PHP approach - memory management didn't matter if entire request (and forked process that handles it) was alive for maximum few seconds.
These issues tend to happen way more in languages that depend on a runtime, especially one with dynamic lookup capabilities. If I remember correctly, log4shell depended on dynamic class loading and a lot of runtime-dependent stuff. Languages that are statically-compiled and memory-safe (namely Go and Rust) don't have the runtime vector and don't generally have the memory safety vectors either. I feel a lot safer deploying services written in Go than JS, for example.
I don't think most people that use PHP use it because they love it and find it a great technical solution, it's mostly technical debt being maintained and the fact that PHP is available to host everywhere.
PHP don't support it and likely won't patch it (even though this is probably big enough that they should), it's up to your distribution whether or not they will.
Many here call for an earlier release of the patch.
But it is not clear if releasing the fix early would make the damage smaller or larger.
Having the patch probably makes creating an exploit easier. So the number of attacks would increase.
There is no way to coordinate the whole world on an earlier time. I would guess the number of people who have to patch their instances is in the hundreds of thousands.
Everybody who actively watches the topic already has the option to shut down their instances.
So ringing the bell and getting as many people as possible to shut down their webservers now and patch at 14:00 might be the best in terms of damage minimisation.
By the way, it is not enough to just "shutdown -h now" and then later restart and "apt update && apt upgrade". The moment the machine comes back, it can get hacked. So you should make sure the webserver does not start after the next boot. For Apache this would be something like "rm /etc/systemd/system/multi-user.target.wants/apache2.service" and then after patching recreate the symlink via something like "ln -s /lib/systemd/system/apache2.service /etc/systemd/system/multi-user.target.wants/apache2.service".
I have not seen confirmation that the exploit is for the bug that is going to be patched.
It seems the published exploit can be easily prevented by filtering out multipart post requests. So people actively watching the situation can already prevent that issue by filtering those.
I was able to bring it to the point of memory corruption. It is 3 am where I am now; I will continue in the morning. As a precaution, I configured .htaccess rule.
# BEGIN php2shell-mitigation
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP:Content-Type} multipart [NC]
RewriteRule .* - [F,L]
</IfModule>
<If "%{HTTP:Content-Type} =~ /multipart/i">
Require all denied
</If>
# END php2shell-mitigation
I added a rewritecond to ignore multipart before php-fpm receives anything. I did a similar thing for nginx servers. Also in .user.ini added "session.upload_progress.enabled = Off".
These two seem to do the trick, but again I am not 1000% sure until tomorrow morning's deeper dive. My eyes are burning, and I can't sleep because of the stress this exploit.
Boom. A leak. It's now a public fact, so we'll instantly see people exploiting it, right? Except that without a commit or patch fixing it, or even a suggestion of a workaround, you are searching for a needle in a haystack. It could be literally anywhere, after all!
In fact, it is so well-hidden that I have not even discovered it myself yet. But its presence is a statistical certainty due to the sheer size of the codebase, so we should assume it is somewhere in there. Did I just doom every W11 user, or are perhaps embargoes at least somewhat useful?
> I feel like all "non-inner-circle people" here are taken for a laugh. OpenAI and these security companies sat on this for 2 months, decided for themselves who gets access to an early fix, and then leave the rest out to dry
Had they just kept this between themselves and the vendor this would've been effective.
Instead they selectively released it to various parties one of which promptly leaked it.
> Having the patch probably makes creating an exploit easier. So the number of attacks would increase.
No matter the excuse, the security issue must be fixed. Anyone trying to delay this is not acting in good faith. I understand your rationale but that does not excuse you from being labelled as such too.
We should live in the age of open source AT ALL TIMES. No exceptions, for anyone, no matter the reasons. And that includes those who want to withhold code or patches.
Honestly, leaving everyone vulnerable and sitting on the patch while the exploits are out in the wild (i.e. no more use of delayed release) is hard to stomach.
A lot of people are going to do the math on migrating. Bugs happen everywhere. Leaving the community out in the cold and only supplying the corporate sponsors doesn't.
How does it work that some service that most people never heard of distributes (paid) images with alleged fix for vuln 24h before official vuln fix/image is available? Seems somewhat shady.
I can almost confirm a Wordpress site I manage was attacked with this. Oct 5th updated it to latest php and Wordpress. Oct 6th it was exploited with a web shell exploit
> Having the patch probably makes creating an exploit easier. So the number of attacks would increase.
I think that this made sense a few years ago but in today's world it is so feasible to give an LLM a hint and throw some cash at it to find an exploit that I don't think this calculus makes sense anymore.
This seems serious enough that I've contacted a few less-technical loved ones about it. I'm warning them of possible scams in the next days, perhaps even hosted on otherwise official pages.
Because some upstream services here in central Europe,
are closed down because of that PHP problem. So now I
am annoyed since this disrupted my workflow.
PHP, please either get your act together - or disband.
I took my services offline last night, wouldn't have been able to sleep otherwise. There has been core PHP members that have outright said the mitigation's currently doing the rounds won't help and even cloudflare can only mitigate against known attack payloads.
The maintainer's comments are singularly unhelpful - "there's nothing you can do, just curl up and die" is pretty useless when you're faced with "take the entire company site offline" vs "maybe get exploited."
Yes, that's not very well done: when you are handling big IT services, you need more than "a person wrote a scary thing on twitter" to justify such an impacting action
The comments aren't unhelpful, they're in fact very helpfully telling you that "take the entire company site offline" is the only safe choice right now.
So what if there are no known mitigations and it's such an open attack surface that logging doesn't help in containing it?
Since you wrote your comment the official blog posts describing what exactly is the in the exploit have been released, and "shut it all down" was definitely the right advice to give.
I initially updated the following php.ini setting and verified that it updated via phpinfo(). I understand this to be only a possible mitigation (see below).
session.upload_progress.enabled = Off
file_uploads = Off
According to someone stating they are one of the PHP release managers:
"INI settings alone won't protect you. You need to patch PHP."
I use Apache, and added an htaccess rewrite rule in my base directory to block all requests containing multi-part headers. Rewrite rules can also be added into Apache virtual host blocks. Accepting file uploads are not a critical function of the app in my case. This blocks multi-part form requests before they reach PHP.
If you're behind CloudFlare apparently they'll cover you, issue is, some people don't have their web servers configured to block traffic NOT from CloudFlare, so it is kind of a bandaid that's falling off I guess.
I'd check this carefully and make sure you have the WAF enabled. I seemed to always have plenty of weird looking PHP and WP requests happily forwarded by CloudFlare to my servers.
Users on the Free plan have access to the Cloudflare Free Managed Ruleset, a subset of the Cloudflare Managed Ruleset.
The only PHP project I had running I took down, it was literally just a web UI for my SQL databases on said box, which wasn't really full of anything meaningful, just old old Discord chatbot logs from forever ago, but still didnt want someone scraping those, so I removed php from the box entirely, I didnt even have a domain for the box so not super worried.
I downloaded the thing, was going to try it out to verify. But the checksum didn't match (probably just a random string generated by an LLM). I left it at that and turned off php.
I've tested the CVEs on PHP 8.5.11 and `session.upload_progress.enabled = Off` definitely increases safety but it doesn't guarantee it. Use of plugins can open up additional exposure.
For those of you using PECL as part of your image build pipeline. I'm seeing timeout issues downloading packages. PECL has been deprecated in favor of PIE. I'd recommend switching to PIE if your build relies on PECL. You don't want to run into this as you rush to update your images.
Major Japanese services like pixiv and e-commerce platforms have elected to turn off services until patches are available. If you're smaller than pixiv, you can afford to go down for a few hours.
I've tried to take one website on a shared hoster down. But I actually can't disable PHP there at all. So no idea if just taking down the website will fix it. Probably PHP won't get executed if no .php files are served, but I'm not sure.
Talked to my clients this morning and persuaded most of them to shut down the services and wait for the patch. For most of them it's cheaper to lose a day of work than to pay for recovery. Scary to be in a situation where you have no fix/workaround in sight.
A reminder, because it really needs to be said, that they spent millions of dollars in tokens for the claimed 11 day sprint, and then spent an additional 3.5 months fixing hundreds of issues it introduced before actually releasing it. Long-term maintainability remains to be seen.
A rewrite would tackle the classic C-style W^X problems, at the expense of maintainability and focus on logic bugs and general oversights from inelegant (or lack of) design. And I'd bet PHP (and popular PHP software for reasons rooted in the language) still got plenty of the latter. You know, the "oops, that filename was client provided" kind of code execution that no amount of (un)safe blocks can help with.
Bun isn't an interpreter. It uses JavaScriptCore for that, which, you guessed it, is C++. As far as I know they have no plans of rewriting it in rust either. Your hot take doesn't seem to apply here.
It's going to be hilarious if I'm not vulnerable because I'm running PHP like it's 1995 via CGI and so get a brand new process per request and break ASLR infoleaks by side effect.
Surprising that this sort of vuln can exist for DECADES. Perhaps software really is too complex for all its behaviours to be outwardly visible. Many student-run services are down right now, even the lunch menu website is going down for maintenance.
I mean we do have examples of how to try to make actually proven and secure software (of course still not absolute), but this is simply deemed to expensive. It's basically the same for every other big problem. We do have examples how to not consume as much resources, as we do now, or how to not shoot explosives at each other. We simply do not want to do it, collectively speaking.
In terms of taking sites/applications down, if you have a maintenance mode that serves only HTML does that seem sufficient at the moment, or is the mere presence of PHP on a server enough right now to warrant "entire server, off button"?
Many modern hosts run php in fcgi mode, where your app is a process that listens on some http port. And where the webserver is "just" a proxy and ssl termination. Shutting down the process is enough.
But traditionally, php was a module loaded into apache. Where apache not only handled ssl, http etc, but also compiled and ran php for you. With that setup, adding an html file, will keep the php runtime and app online.
The previous presence of PHP and its oftentimes ridiculous common practices might mandate a maintenance mode that is a little more involved than just serving HTML.
I'm not seeing any discussion here about woeful web application architectures from the 1990s still in use?
The single biggest problem I came across over a decade ago when maintaining an open source PHP web application was web applications at the time typically having access to a common database server role (often also common between users and administrators) which allowed a web application process to read and sometimes write to the entire database. No use of user-specific roles in database servers and row-level-security/column-level-security authorisation. At the time I don't think PostgreSQL even had row-level-security support built into it. A runaway PHP process could return the entire database to the attacker, or change every single row of data held within the database.
The second biggest and related problem was web applications accepting files uploaded from users, or having to generate reports (maybe with external software) and save them to disk for a user to download, and not being able to ensure a runaway PHP process can't just dump all of those files or reports to an attacker. You might have been able to store the user files (or at least a decryption key for the files) in a database but then you're back to dealing with problem (1) above.
Even a decade ago it was fairly common for web application developers (of the PHP sorts too) to be well aware of the need to make their web root read-only, put the web application source code into a read-only directory outside the web root, execute interpreters such as PHP with "nobody"-like permissions, launch a new interpreter process for each connection (not multiple threads within the same process), firewall off the server the web application sits on so a runaway PHP process can't connect to internal servers, etc. Outside of an attacker messing with a database, most other aspects of PHP web applications at the time were immutable if the web application developer / system administrator had setup the environment correctly.
Is there a solution for (1) and (2) for PHP web application development that has become popular in the proceeding decade?
edit: also nominating the shared $_SESSION state of PHP that was typical a decade ago to just be left to default (e.g. all PHP processes just read/write session files to a common /tmp directory). https://www.php.net/manual/en/function.session-set-save-hand... should probably instead be used by web application developers to somehow better isolate session state between users.
As far as I can tell none of this is related to the current vulnerability in PHP itself. Even having a site that just returns echo "phone us on XXXX" is vulnerable apparently.
A dynamic language having access to all of the files it has access to is not unique to PHP. Vulnerabilities are not unique to PHP, and I doubt the Dutch National Cyber Security Center took their website offline because they lack user-specific roles in the database: https://www.ncsc.nl/index-en.html
So maybe save your elitism for a day when so many of us aren't already putting out fires? Congratulations on not being part of the 75% of the internet affected.
The question to ask is should these defaults be tightened. For example, disallow read and execution of anything outside /var/www/, such as /usr/bin/sh. For example, block syscalls PHP won't ever use to limit chance of a compromised PHP process being able to utilise a LPE kernel vulnerability. And then update user installation documentation to explain the onus is on the user to open up very restrictive default permissions should they really have a need to do so.
PHP is definitely more at risk of this class of vulnerability because fatal errors are longjmps which skip resource clean-ups. In a runtime with real unwinding, this exploit class can't exist.
> Even having a site that just returns echo "phone us on XXXX" is vulnerable apparently.
Vulnerable but perhaps with no impact. If you've setup your web server well, the vulnerable PHP process is sandboxed, at least to some degree, and an attacker executing their own code within the compromised PHP process can't move laterally through your internal networks, write files to disk, read files from disk, etc because you've locked down the PHP process.
In 2026, perhaps it's possible to:
1. Use systemd socket activation with Accept=yes [1] and strict sandboxing applied to a systemd service that executes the PHP interpreter. The result being each incoming request is dealt with inside an isolated PHP process spawned specifically to handle the request. Compromise of a PHP process doesn't impact any other concurrent requests, or any future requests, except through defined sandbox interfaces such as access to a database server socket.
2. For each user of the web application (perhaps including an 'anonymous' user too if anonymous users have access to dynamic content), if using PostgreSQL, create a role in PostgreSQL for each web application user. Then use row-level-security permissions and security barrier views within the database, and have the PHP process accept credentials from the user which are then needed to be passed through to PostgreSQL to login as that individual user.
It's not without some significant downsides:
1. It's complex and you might be the only person in the world trying to use PHP in this secure way. And if you're going this far, for a complex web application, it'd be best to split it into smaller web applications each with their own systemd service defining specific sandboxing constraints. E.g. microservice architecture where "login", "file upload", "user administration" are all separated with different sandboxing constraints applied to each.
2. Performance will suffer and you'll need more resources--for spawning new PHP processes from scratch for each request (although this is already the case with php-fpm which is most widely used), and for dealing with row-level-security in PostgreSQL (see e.g. LEAKPROOF functions).
The more common pattern I've come across on public websites in recent times that might mirror some of the above is client-side JavaScript dynamic rendering with API calls to a GraphQL database exposed on the Internet (using e.g. field-level access control). The user isolation problem is essentially pushed from PHP+PostgreSQL to a GraphQL implementation.
PHP has been the worst thing to happen to the web. It was insecure many decades ago and still is. Even CGI with C is probably more secure, never mind technologies like Java, ASP.NET and Rust with are far more secure.
I even have a preference for web stores which use ASP.NET or Java since I know my personal information are safe there.
There are probably thousands of web stores using PHP unwittingly too. I've noticed only about half of them have been taken offline.
I like PHP and I use it everyday. What concerns me about incidents like this isn't just the vuln itself, but how much access a compromised PHP process can have to the rest of the system.
Kind of seems like they just shut down their PHP service like everyone else... If this is the case, hopefully they can set up a temporary static site to inform about relevant updates.
So all local universities have now essentially shut down
their web-services for students. This is ... kind of
curious because now you can not download recent updates
(e. g. new .pdf files published) from that software.
We need a long-term solution with regards to PHP. PHP
is a success story - so much web-software depends on it.
But it also has become a liability when they are all now
scared that the server can be easily taken over. This is
not acceptable, PHP.
PHP has been a security dumpster fire for decades. It's just how the entire web ecosystem works: some web designer lacking any technical know-how is asked to make a site and dumps WordPress on it out of habit.
Even though there are much more secure CMS technologies out there like Umbraco or Piranha (both ASP.NET) and web stores like NopCommerce (ASP.NET also).
There are just too many technically clueless people building web sites and web stores.
>PHP 8.1 and older no longer receive updates from the PHP project. Some distributions and LTS vendors provide backported fixes, so contact your vendor for details, or upgrade to a supported version.
I get that maintenance teams need to have conviction in this approach, but this is definitely going to cause catastrophically large data breaches downstream.
> Given the severity of these vulnerabilities, the PHP security team provided minimal source-backports for PHP 7.4, PHP 8.0, and PHP 8.1 to help people building from source or without access to an LTS vendor.
None of these 2 CVEs seem relate to POC spread in twitter. I'm not sure if the POC is something fake or they just unveil something within a few hours..
Scroll down in the actual patches to the weirdness of the multipart parser. That very much looks related to the what can be abused via the upload progress callbacks that had been discussed on (anti)social media.
At this point, it would be fastest/most effective for the PHP foundation to deploy their own white-hat mass hacking attack to exploit the vulnerability and forcefully shutdown vulnerable servers.
I can't think of a faster way to clear out the vulnerable surface area.
Yeah they should poorly set up a sandbox and ask it to fix all the vulnerable servers with the remote RCE and prepare to be surprised when it escapes the sandbox.
$ docker pull php:8.4.27
8.4.27: Pulling from library/php
no matching manifest for linux/arm64/v8 in the manifest list entries
$ docker pull --platform linux/amd64 php:8.4.27
8.4.27: Pulling from library/php
no matching manifest for linux/amd64 in the manifest list entries
What steps can someone take to determine if they might have been hit?
So far, I have checked to see if any new files have been placed in our directories or if there have been any file changes. I've also looked at the access logs for unexpected POST requests.
If your application is known to routinely "deserialize" (unsafe-eval) strings from a database or cache, an attacker might have placed a tiny backdoor that way, only to be used after the everyone has applied the PHP patches and attention levels & active staff are back to normal.
I actually looked through PHP code responsible for parsing POST request body and it's pretty bad [1].
First, there is a huge function, that is hard to read and reason about. Second, instead of proper parsing of "Content-Type" header to extract "boundary" parameter, there is just a set of substring searches which is not correct. It doesn't mean there is a vulnerability but it means PHP can read the header in a way different from a standard-compliant implementation (such as web server, WAF etc).
how does Docker not yet have a new, official PHP image ready? https://hub.docker.com/_/php Nuts this wasn't ready to flip on at :00 (or even earlier given the PoC exploit and even the official PHP fixes were out well before). Now we are :20 minutes past due. Everyone had a multi-day heads up, this is negligence
I would really like a list of all major websites using PHP so I can continue to avoid ever using them again (something I already try to do). This whole situation should make it clear who was affected by their downtime in response.
Gigachad | 22 hours ago
I think the best course of action is to just shut your server down before the patch goes live and then bring it back after you have patched.
archon810 | 21 hours ago
philipwhiuk | 21 hours ago
Gigachad | 19 hours ago
lioeters | 19 hours ago
voxadam | 18 hours ago
https://www.schneier.com/blog/archives/2005/12/benevolent_wo...
lioeters | 18 hours ago
stackghost | 18 hours ago
S0y | 17 hours ago
afdbcreid | 16 hours ago
pixl97 | 16 hours ago
afdbcreid | 15 hours ago
jamesknelson | 14 hours ago
Turning it off may cause deaths. Letting it get ransomwared may cause more. Do you pull the lever to turn it off?
hparadiz | 14 hours ago
You make sure www-data CANNOT write ANYWHERE on disk. Not /tmp/ Not to /var/www/. No where.
Then make sure your sudoers has nothing weird in it.
Finally disable www-data's ability to run basically anything that isn't required for the operation of your httpd or php-fpm et al.
You then harden it further and further until an RCE does not matter because it's incapable of doing anything.
tldr always treat httpd as untrusted.
trog | 13 hours ago
hparadiz | 13 hours ago
trog | 13 hours ago
throwaway270925 | 9 hours ago
Did this with my parents websites and they are quite happy and I get basically no support calls (and can read threads like this one out of interest only, thankfully)
trog | 5 hours ago
bpye | 13 hours ago
And also relies on the target being patched against any Linux EoP...
matja | 12 hours ago
Also: https://stopdisablingselinux.com/ - SELinux can mitigate this.
echoangle | 12 hours ago
1718627440 | 9 hours ago
pixl97 | 7 hours ago
"How to make your site cost unlimited money and have terrible performance". People did this in the Web 1.0 days on occasion and it leads to all kinds of problems for any site with any kind of traffic.
>Or you make an exception for them.
Useless. All you need to do at that point is chain a priv-esc to your existing exploit and you get root.
simondotau | 15 hours ago
1718627440 | 9 hours ago
simondotau | 8 hours ago
elondaits | an hour ago
qingcharles | 18 hours ago
rklaehn | 13 hours ago
bigbuppo | 14 hours ago
dylan604 | 13 hours ago
geerlingguy | 10 hours ago
asimovDev | 11 hours ago
ndiddy | 18 hours ago
ChrisArchitect | 20 hours ago
jamesfinlayson | 20 hours ago
gnabgib | 20 hours ago
https://cert.europa.eu/publications/security-advisories/2026...
> affect PHP versions 5, 6, 7, and 8.
https://www.bleepingcomputer.com/news/security/php-warns-adm... (which references HN as a source - https://news.ycombinator.com/item?id=50167754)
Operyl | 18 hours ago
gnabgib | 18 hours ago
cesarb | 18 hours ago
Probably the same way log4j 1.x avoided log4shell: the vulnerable code was introduced on a later release.
Perz1val | 13 hours ago
B: "5.6, 7, 8“
A: fixes a "typo" ok so "5, 6, 7, 8"
jacquesm | 20 hours ago
stingraycharles | 19 hours ago
SyneRyder | 19 hours ago
geerlingguy | 17 hours ago
Tadpole9181 | 16 hours ago
jeroenhd | 16 hours ago
The PoC also requires a known binary to exploit so custom PHP builds may be safe if you're lucky, but this seems to be an extremely bad one.
LoganDark | 20 hours ago
php.ini:
lynndotpy | 19 hours ago
LoganDark | 19 hours ago
xena | 19 hours ago
lynndotpy | 19 hours ago
I shut down my servers five hours ago. This might have seemed premature at the time.
I think the best course of advice for most people is to shut down their servers as soon as they possibly can.
qingcharles | 17 hours ago
lol768 | 19 hours ago
Are you speaking officially here?
There are various mitigations suggested online, including completely blocking multipart requests at LB level. Is the combination of both effective?
lynndotpy | 18 hours ago
I don't think pulling mitigations from random users online during a developing situation is a good idea. I think shutting down ones PHP services for the time being is a very good idea if that's an option.
1over137 | 18 hours ago
pickledish | 17 hours ago
ThePowerOfFuet | 17 hours ago
robwayne | 18 hours ago
https://phpc.social/@Girgias/117476477429221001
joshuat | 19 hours ago
bakugo | 19 hours ago
atymic | 19 hours ago
mschuster91 | 14 hours ago
> Two cached bucket pointers, one freed tree.
I've rarely been happier than now to have left IT for good...
nicce | 14 hours ago
meibo | 14 hours ago
duozerk | 12 hours ago
You immediately know you're likely to get clear, technical, actionable info instead of some corporate bullshit
Not so with LLM usage
Perz1val | 13 hours ago
mschuster91 | 10 hours ago
But I'm reading a website for getting information, not LLM fluff.
cinpol | 13 hours ago
redox99 | 19 hours ago
spenvo | 19 hours ago
https://x.com/MagicalTux/status/2112725774025572431 https://x.com/rina4_tot/status/2112723421641531772
I think this exploit + agentic AI (which allows for rapid secret exfiltration/utilization) may be a potent enough combo to trigger a sort of Kessler Syndrome for network security.
int32_64 | 18 hours ago
TacticalCoder | 13 hours ago
And he went to prison for a few years for it. So he knows something about PHP exploits.
NorwegianDude | 8 hours ago
defgeneric | 17 hours ago
matkoniecz | 14 hours ago
why it would be a thing, beyond "serious problem"?
sippingabonedry | 14 hours ago
Yeah no.
This is bad but doesn't even crack the top ten.
tikotus | 13 hours ago
bguebert | 7 hours ago
sippingabonedry | 2 hours ago
At the end of the day, nobody gives a shit if another WordPress blog gets hacked.
Narkov | 13 hours ago
lol no.
I feel old. Heartbleed was 2014.
bpye | 13 hours ago
ameliaquining | 13 hours ago
Fabricio20 | 13 hours ago
manarth | 12 hours ago
Fabricio20 | 11 hours ago
Extremely legacy software wasn't affected either (log4j v1 or apache commons-logging!). Lots of automated scanners flagging the idle jar as well (when the app used Logback for example as the SLF4J implementer, but the scanner saw a transitive for the log4j jar and would scream at you - that's when I stopped caring about github vuln scans btw, it was a shitshow).
Like dont get me wrong, it was a bad vuln, but to me it seems like it was more hype machine and internet screaming than actual vulnerable applications. I do recall Minecraft was vulnerable though, that one was indeed a big target given publicly exposed servers and such.
kllrnohj | 9 hours ago
ndriscoll | 7 hours ago
evandrofisico | 6 hours ago
joshuat | 12 hours ago
Measuring “worst” is hard.
echelon | 11 hours ago
Thanks, PHP.
dangoodmanUT | 19 hours ago
I got into software dev because of cyber sec, and almost everything I learned revolved around poorly implemented php, so I always stayed away from it when building
but this time it's php directly? that's scary
mircerlancerous | 19 hours ago
Gigachad | 18 hours ago
If the rumors going around are true this will be the worst computer security incident in history.
afdbcreid | 17 hours ago
altmanaltman | 16 hours ago
sdfgsdfgsdsdfgs | 16 hours ago
Tadpole9181 | 16 hours ago
Usually, attacks are at least conditional and require something that weakens security guarantees.
sdfgsdfgsdsdfgs | 16 hours ago
Tadpole9181 | 15 hours ago
dgrunwald | 15 hours ago
log4shell was easier to exploit. It also come with an initial patch that turned out to be incomplete, so everyone had to urgently patch every java web app twice!
Freak_NL | 14 hours ago
Still a very large attack surface, but not nearly as ubiquitous as this one.
eithed | 14 hours ago
nullbio | 19 hours ago
hparadiz | 18 hours ago
enews01 | 18 hours ago
1over137 | 18 hours ago
72deluxe | 12 hours ago
Xiol | 11 hours ago
0xbadcafebee | 11 hours ago
jumperabg | 11 hours ago
jeffbee | 18 hours ago
Operyl | 18 hours ago
jeffbee | 18 hours ago
Operyl | 18 hours ago
jeffbee | 16 hours ago
It isn't 1998 any more and you can no longer just inject shell code on the heap.
Operyl | 16 hours ago
jeffbee | 16 hours ago
Operyl | 16 hours ago
bulatb | 17 hours ago
You could do that to an internet-connected toaster with a JPEG. The system() function has nothing to do with it.
afdbcreid | 18 hours ago
reorder9695 | 14 hours ago
calvinmorrison | 18 hours ago
Shell access is not good, but in many places that wouldn't be the end of the world either.
Rethink your strategy
Operyl | 18 hours ago
charcircuit | 18 hours ago
At least this time we can have LLMs rediscover it and make patches ourselves.
Here is the patch I had an LLM come up with against master: https://pastebin.com/raw/EUCF0SR0 It at least stops the PoC which is better than nothing.
bwoebi | 18 hours ago
There are a handful people responsible for doing a release. They are still asleep.
To be honest, I am also shocked, that the exploit was published that quickly, after the leaked video (which was the reason, why the announcement happened in the first place, at that specific time). We expected a bit more time, even with LLMs...
jwitthuhn | 17 hours ago
heresie-dabord | 15 hours ago
This is something of a fallacy. "The Industry" cannot learn.
But laws and regulations can require better security.
As in the history of seatbelts in vehicles, tech tool stacks are insecure by design and no one is ever really held accountable... until the cost is deemed too high.
It's evident that we have not reached that limit yet.
my-huge-pony | 14 hours ago
ameliaquining | 13 hours ago
mx7zysuj4xew | 7 hours ago
jwitthuhn | 13 hours ago
What they have achieved by delaying the patch is that exploits are now available publicly before a patch.
Surely this is the worse outcome.
merb | 9 hours ago
Also not announce it beforehand…
compass_copium | 8 hours ago
ftfyyyyyy | 15 hours ago
dlor | 15 hours ago
The vulnerability and patch are both very complex, and the maintainers did an incredible job on this one. We tested the patch extensively and it's holding up well.
We've made these images free and will keep them that way.
aarondf | 15 hours ago
thenaderman | 13 hours ago
tarsinge | 11 hours ago
shakna | 11 hours ago
nagaiaida | 3 hours ago
shakna | 2 hours ago
Why would you implicitly take them at their word?
nagaiaida | 12 minutes ago
as it stands though, what i replied to wasn't a useful addition to the discussion. it could easily become so by either being made contingent upon the possibility of that being a lie, or being bundled with an assertion like yours that chainguard is not to be taken at their word. doing neither and simply responding as if a causally opposite statement had been made is just a non sequitur.
nicce | 10 hours ago
charcircuit | 8 hours ago
b112 | 5 hours ago
If you want to 'adopt' a new reality, you talk to all parties, and everyone moves up the release. That's how agreements and trust work. If you don't do so? No one will trust you ever again.
And?
You won't be at the table next time.
threatofrain | 3 hours ago
If the first party to receive this information says, "Wow, of course I must act on this, because customers are on the line," then it makes sense to simply choose who you tell more carefully or not at all.
Roark66 | 7 hours ago
dhruvagoyal | 3 hours ago
rgj | 3 hours ago
"We took our website down this morning when the "PoC"s were released, only serving a static website. Our customers were not pleased. Then we got contacted by Chainguard affiliates using our public support form if we would like to schedule a meeting with them, so that they could sell us their security services."
summner | 14 hours ago
anything that narrows the searchspace
thenaderman | 13 hours ago
Shank | 13 hours ago
joshuat | 12 hours ago
jacquesm | 12 hours ago
That's horribly naive with an installed base this size and if you are that geographically dependent then I would hope to read how this will be dealt with going forward.
Macha | 9 hours ago
jacquesm | 8 hours ago
I think you are assuming I am running PHP which I haven't used in production for more than a decade. That doesn't change the fact that if you power this many websites that you should have a plan in place for when there is a critical issue.
barelysapient | 18 hours ago
tonymet | 18 hours ago
skoskie | 18 hours ago
system2 | 16 hours ago
Synthetic7346 | 15 hours ago
system2 | 15 hours ago
reddalo | 14 hours ago
aksss | 17 hours ago
aussieguy1234 | 17 hours ago
mappu | 16 hours ago
minitech | 14 hours ago
aussieguy1234 | 13 hours ago
https://nodejs.org/en/blog/vulnerability/october-2026-securi...
minitech | 13 hours ago
mappu | 17 hours ago
lolakutty | 17 hours ago
qwm | 13 hours ago
dawnerd | 18 hours ago
burnJS | 17 hours ago
dawnerd | 17 hours ago
But created my own based on it since it feels sketchy running someone else's exploit poc ya know. Ran it first in a vm before running it against a production site.
burnJS | 17 hours ago
afdbcreid | 17 hours ago
system2 | 14 hours ago
normie3000 | 14 hours ago
dan15 | 13 hours ago
It still uses the same request model as PHP, since that's genuinely useful for web requests. It's easier to avoid memory leaks if each request is entirely self-contained and there's no global state persisted between requests (other than APC and opcode caches)
rob | 9 hours ago
https://x.com/levelsio
doublerabbit | 8 hours ago
system2 | 2 hours ago
rurban | 2 hours ago
sznio | 16 hours ago
brazzy | 14 hours ago
tikotus | 13 hours ago
td4 | 12 hours ago
it now serves ads that instantly start those downloads its been like that for a couple of weeks
dvdkon | 12 hours ago
sdfgsdfgsdsdfgs | 16 hours ago
cinpol | 13 hours ago
dwedge | 11 hours ago
stackghost | 17 hours ago
burnJS | 17 hours ago
00deadbeef | 16 hours ago
rokkamokka | 15 hours ago
voidUpdate | 12 hours ago
doubled112 | 9 hours ago
doublerabbit | 8 hours ago
burnJS | 9 hours ago
theteapot | 17 hours ago
burnJS | 17 hours ago
lolakutty | 17 hours ago
Of being a hole...
winternett | 15 hours ago
febed | 14 hours ago
rossriley | 14 hours ago
fg137 | 10 hours ago
berkes | 9 hours ago
Not only 10 years of no more security updates. But hosting static content is cheap, performant and sustainable. Bot literally (you can move the content anywhere, using any kind of server) and in energy sense.
While I understand it is not for everyone to write markdown files and run build commands, I strongly urge anyone with a WordPress or drupal site to give the various jamstacks, or static site builders and guis a test run.
dwedge | 9 hours ago
dawnerd | 6 hours ago
redox99 | 18 hours ago
Titan2189 | 17 hours ago
buzer | 17 hours ago
xyst | 17 hours ago
With vibe coded slop tools readily available, using php in 2026 is just laziness.
alberth | 17 hours ago
https://xitter.cf/k_firsov/status/2112718728232329240#m
xyst | 17 hours ago
Titan2189 | 17 hours ago
CookieCrisp | 17 hours ago
jdiff | 17 hours ago
https://phpc.social/@Girgias/117476510850918355
https://old.reddit.com/r/PHP/comments/1xb2utu/comment/phyu5m...
exodust | 15 hours ago
Further more, if in Australia or a few other places like Brazil, UK, France, reddit won't let you sign in at all unless you're proven to be over 16. Bottom line, linking to old.reddit is similar to linking to a paywalled article.
rasz | 14 hours ago
1718627440 | 8 hours ago
simondotau | 17 hours ago
If they can't, why not?
If they can, why haven't they already?
marcins | 17 hours ago
georgemcbay | 17 hours ago
The original exploit, and then when the rumors of a big critical patch got out, the people who are leaking the details online probably used an LLM to find the exploit again.
Just revealing that an unpatched exploit exists in $XYZ these days basically guarantees that a bunch of people are going to target $XYZ with LLMs looking for that exploit.
simondotau | 17 hours ago
georgemcbay | 17 hours ago
Well, that would be super nice of them.
From a Machiavellian standpoint it may benefit the people with the most powerful models to let some serious RCEs like this PHP one get widely exploited in damaging ways to further their regulatory capture argument that open weight models have to be legally banned and only locked down models with enforced guardrails around usage can be allowed.
simondotau | 13 hours ago
From a marketing standpoint, having the first model to find a bug of this magnitude and severity would be a pretty damn impressive proof of capability. Finding previously unknown, critical vulnerabilities in widely used open-source software could become a gold-standard test of frontier AI competence.
SyneRyder | 15 hours ago
Either Mythos is useless and didn't find this (hint: Opus 5.5 will find this once it knows where to look)... or, they did find it, and this is one of many vulnerabilities they're covering up via "guardrails".
I'll be a lot happier if I wake up tomorrow and find this was found with help from Anthropic (or even OpenAI) but I won't hold my breath.
shepherdjerred | 17 hours ago
simondotau | 17 hours ago
afdbcreid | 16 hours ago
If you only tell them to find issues in PHP - the strongest models probably still can, although they might find different issues ;)
nikanj | 10 hours ago
The bad guys have invested the resources of the criminal enterprise into hardware running unrestricted models.
t1234s | 17 hours ago
adventured | 17 hours ago
Gigachad | 17 hours ago
ipaddr | 16 hours ago
shepherdjerred | 17 hours ago
I know there must be a ton of random sites which makes this a huge deal.
But, does it affect any big players? I think php is big at Meta but I would imagine its so heavily customized it might be safe from this.
guskel | 16 hours ago
MrVandemar | 16 hours ago
Just as a scripting language on my own laptop, nothing prod. But one thing I notice, even coming back to it after a little while, even after using Python for everything, I find I am effortlessly productive with it.
There was an article I read recently about a blind developer who finds it easy to write in, as the "$" for the variable names makes it easier for him to identify what's going on in any given line of code.
Like any language it has advantages and disadvantages.
accountrequired | 12 hours ago
garbagepatch | 15 hours ago
aksss | 15 hours ago
trollbridge | 14 hours ago
bigbuppo | 14 hours ago
dofm | 15 hours ago
reddalo | 12 hours ago
Good4boothee | 12 hours ago
vanschelven | 10 hours ago
[0] https://modat.io/blog/php-exposure-before-the-21-oct-2026-se...
ernubufiei | 17 hours ago
metax | 17 hours ago
redox99 | 17 hours ago
afdbcreid | 16 hours ago
pixl97 | 16 hours ago
jeroenhd | 16 hours ago
If you put the oauth wall in front of the application before it can even reach PHP (i.e. in your nginx/caddy/apache config), then no, assuming all paths are covered.
pja | 12 hours ago
This looks like a bug in PHP’s assembly of multipart responses & you can feed one of those to the PHP backend with a simple web request, no auth required I think.
aksss | 17 hours ago
Of course you can do this with web server (eg Apache) config as well, but the CF rule is something you can do now on your phone.
I’m not saying I know this works as a mitigation, but it seems like it could at least contribute to a temporary guard until you get patch in place. Everything I’ve seen about the exploits seem to revolve around multipart form submissions.
solyin | 16 hours ago
aksss | 16 hours ago
rgj | 12 hours ago
vincent_s | 16 hours ago
1. Turn off session upload progress
2. Block multipart requests at the web server
More info: https://www.vincentschmalbach.com/cve-2026-109618-and-cve-20...
Gigachad | 16 hours ago
rasz | 14 hours ago
is this multipart request smuggling again?
edelbitter | 12 hours ago
top_sigrid | 11 hours ago
vincent_s | 10 hours ago
jtchang | 16 hours ago
system2 | 16 hours ago
throwaway82931 | 16 hours ago
They're on top of it as I would expect any major PHP hosting service to be. After asking if there was anything I could do to prep for php2shell (seemingly not), I just pleaded to be first in line when they apply patches and let them go.
How are others in similar situations handling this?
aksss | 16 hours ago
Therefore, a temp mitigation that runs short of shutting your site down is to temporarily block POST requests until you can get the patches in place. This will screw up any form functionality, including your WP login form, but keeps your site presence up. A failed form submission is probably a better look than no site presence. You can affect this with Apache config or by using a WAF. For instance if you have cloudflare caching your domain, use a free security rule to block all POST requests until your patches are in. Something like `http.request.method in {"POST" "PUT" "PATCH" "DELETE"}`
throwaway82931 | 14 hours ago
lxxvii | 13 hours ago
aussieguy1234 | 16 hours ago
ronsor | 16 hours ago
sdfgsdfgsdsdfgs | 16 hours ago
So, theoretically, if you wanted to hack a server but you don't know what OS/PHP, version they're running, you could compile a list of every delta for every litespeed release and then bruteforce it, right?
lossolo | 16 hours ago
herpderperator | 14 hours ago
viraptor | 10 hours ago
herpderperator | 4 hours ago
So, if the offsets were in fact different, would the explots still work? (I think the answer is actually yes based on what I read/saw; I think the PoC dynamically calculates these offsets? Not 100% sure, but we shouldn't take chances.)
viraptor | 10 hours ago
throwaway800BC | 16 hours ago
Fil-C should have caught this right? I wonder if it would benefit the PHP ecosystem as a whole if the releases are built with it instead.
epse | 14 hours ago
dl | 16 hours ago
codedokode | 16 hours ago
JSalinasAtTER | 16 hours ago
matkoniecz | 13 hours ago
Mooty | 15 hours ago
Here is an Nginx patch : if ($http_content_type ~* "multipart") { return 403; }
You can also turn of session progress in php.ini as mentionned but that does not seem to cover every cases : session.upload_progress.enabled = Off
trog | 15 hours ago
Mooty | 15 hours ago
It assumes PHP frees the upload progress data when it reloads the session. But PHP 8.4 (the one we use is 8.4.24, i don't know for other versions) calls Z_TRY_ADDREF(progress->data) to keep that data alive. The fake function call also seems to contain invalid fields.
This makes me question this particular PoC, not the official PHP security warning. I have not reproduced the exploit, so this is a concern based on reading the code, not proof that the real vulnerabilities cannot be exploited.
But anyway the CVE still exists, and the exploitation is tied to multipart, disabling it seems the best thing you can do now without shutting everything down.
nikanj | 15 hours ago
cinpol | 13 hours ago
top_sigrid | 11 hours ago
system2 | 15 hours ago
reddalo | 12 hours ago
poilcn | 12 hours ago
ctolsen | 12 hours ago
system2 | 3 hours ago
Tepix | 11 hours ago
joshstrange | 9 hours ago
hn_submit | 15 hours ago
PHP contains an almost endless stream of vulnerabilities since its inception almost 3 decades ago. Proponents claim that it's getting better but this just goes to show that nothing's changed.
arjie | 15 hours ago
EDIT: Ha, Claude just took the blog and rendered all pages and now it is a static site! I'll restore the Mediawiki once I can fix the issue.
anthonyeden | 15 hours ago
The Alpine GitLab[1] indicates the PHP versions to be released 21-10-2026 14:00:00 UTC are:
8.5.12 8.4.27 8.3.36 8.2.35
[0] https://developers.cloudflare.com/waf/change-log/changelog/
[1] https://gitlab.alpinelinux.org/groups/alpine/-/work_items?sh...
ksenzee | 15 hours ago
trog | 13 hours ago
joshuat | 12 hours ago
> WP Engine Security and Engineering have enabled WAF rules for all customers using GES and AN. Mitigations are currently being deployed across the rest of our infrastructure, and official patches will be applied as soon as they become available.
ErikRogneby | 4 hours ago
tro2102 | 14 hours ago
anthonyeden | 14 hours ago
edelbitter | 14 hours ago
consp | 13 hours ago
vesinisa | 11 hours ago
reddalo | 12 hours ago
viraptor | 10 hours ago
iamniels | 10 hours ago
SweetSoftPillow | 5 hours ago
bilekas | 9 hours ago
https://x.com/BunnyCDN/status/2112867273333485634
lousken | 6 hours ago
lousken | 2 hours ago
rasz | 14 hours ago
<p>Due to an <a href="https://www.php.net/archive/2026.php#2026-10-20-1">upcoming significant vulnerability disclosure</a> with no official mitigation, services are currently offline as a precaution. Services will not be restored until at least later in the day on October 21. This time may also be spent on additional maintenance, so this message may be periodically unavailable.</p>
matkoniecz | 13 hours ago
> The OpenStreetMap.org operations team have decided to temporarily shutdown a number of key secondary OSM.org services due to a critical PHP security vulnerability.
sippingabonedry | 14 hours ago
Someone on X mentioned the bug relies on some kind of ASLR bypass.
djriley | 12 hours ago
Php2shell is completely language level. By the time the OS sees it it's just a function of the webserver.
vwelling | 14 hours ago
tikotus | 13 hours ago
CawCawCaw | 13 hours ago
https://emudhra.we-have-a-problem.com/
moebrowne | 11 hours ago
AndroTux | 12 hours ago
joatmon-snoo | 13 hours ago
tikotus | 13 hours ago
I had to shut down my own backend services. Luckily a big part of my service can run on a static website.
tommica | 13 hours ago
Good4boothee | 12 hours ago
dubeye | 13 hours ago
so even if it takes a few days to get my AI agent to do this, it's still a vastly more secure landscape for an amatuer like me
Gigachad | 13 hours ago
dubeye | 13 hours ago
Anyway my point is I'm much less likely to get hacked in this new era of AI assistance, as I'm only a few days behind, rathe than a few months or years behind.
00deadbeef | 12 hours ago
Security researchers expect mass attacks within 15 minutes of disclosure.
dubeye | 12 hours ago
basilikum | 12 hours ago
juliusjh | 12 hours ago
Yes, but also, attackers are much faster now and complex chains of vulnerabilities became much easier to carry out. In the past, you might have just been "secure" because nobody cared to put in the time to target you unless you were unlucky. Now, many people have the capability and can completely automatize it.
We essentially had security through obscurity for a long time. It was always dangerous. It's good that it ends. But the transition might be rough.
dubeye | 12 hours ago
I'm not seeing reports of dramatic increase in hacks.
It will be interesting test case today, will we see huge amounts of hacks or not.
juliusjh | 12 hours ago
Maybe the effort and required hardware of running an LLM locally have so far prevented widespread exploitation? Maybe open-weight LLMs are too far behind at the moment? Maybe it's happening but we didn't notice it for some reason?
I would strongly assume that it will happen at some point if it isn't already.
dubeye | 12 hours ago
in my experience AI is helping me defend against potential vulnerabilities, and so the net impact of these threats is net zero or less, even if I'm quite slow in patching stuff
nkozyra | 12 hours ago
The AI assistance you need is "rewrite this in something else"
joshuat | 12 hours ago
Expect the entire ipv4 space to be crawled for this with common paths being attempted.
hakube | 9 hours ago
tredre3 | 5 hours ago
Your agent can't help you before the patch is rolled out, so let's not lose sight that the fix to this vulnerability will be:
apt update && apt upgrade
If you didn't know how to keep your server up to date before agents, then perhaps a managed hosting service would be a better fit?
janmo | 13 hours ago
https://x.com/dok2001/status/2112811965735202970
When will they finally release the patch?!
SSLy | 13 hours ago
mattbee | 12 hours ago
When a PoC drops before that timeline is up (like now!) the attackers get a head start because they have less work to do - just figure out how to use it to their payload, start spraying it out.
Meanwhile maintainers don't want release an incomplete or misunderstood fix. Otherwise they'd risk people updating and believing that they're safe when they're not. Even a fragment of misinformation from an official channel will spread like wildfire. So when you demand fixes NOW you're demanding something that may not be completely understood.
So (I'm sure we'll find out but) I believe this 2pm timeline was already as soon as is human possible for the PHP team to do a repsonsible job, and not risk us having to come back tomorrow for a fix to the fix.
LLMs gives attackers the advantage for a while, and it means we'll have to tighten the secrecy around even the rumour of a vulnerability.
SSLy | 12 hours ago
https://cyberplace.social/@GossiTheDog/117477870253346830
xena | 10 hours ago
stevage | 9 hours ago
Dylan16807 | 12 hours ago
> I believe this 2pm timeline was already as soon as is human possible for the PHP team to do a repsonsible job
I'll be surprised and kind of upset if the fix wasn't already done when they announced the bug and the sub-24-hour release time.
oceansweep | 5 hours ago
uselesswords | 4 hours ago
SSLy | 4 hours ago
bombcar | 11 hours ago
Hamuko | 11 hours ago
bombcar | 8 hours ago
pxtail | 13 hours ago
janmo | 13 hours ago
Numerlor | 13 hours ago
This would've worked if other people were able to shut up about it. Because its existence got leaked they posted the announcement
hparadiz | 13 hours ago
Dylan16807 | 12 hours ago
janmo | 12 hours ago
This lets an AI agent look at the changes made from PHP 4 to PHP 5 and it also lets the agent guess what type of vulnerability it must be.
0xbadcafebee | 11 hours ago
viraptor | 11 hours ago
I mean an agent can walk those changes, but it's close to just walking all the whole source / research from scratch at that point.
Dylan16807 | 10 hours ago
wink | 9 hours ago
ndiddy | 9 hours ago
charcircuit | 8 hours ago
Numerlor | 12 hours ago
At this point shipping the build already may have been the best option but not necessarily everyone is actually able to ship yet. And this is of course assuming the actual vulnerability is the same one as the PoCs that are being tried, and not something even nastier instead
mx7zysuj4xew | 7 hours ago
Gigachad | 12 hours ago
nananana9 | 12 hours ago
reddalo | 13 hours ago
montag | 12 hours ago
Mojah | 13 hours ago
https://ma.ttias.be/php-cve-2026-109618-early-mitigation/
petesergeant | 13 hours ago
> Both block automated requests, so I could not check their text myself.
Are you automated?
Mojah | 13 hours ago
m3nu | 10 hours ago
minraws | 13 hours ago
nr378 | 13 hours ago
The upgrade instructions here should include torching your hosts and starting again.
sparkling | 12 hours ago
- Any PHP site you ever put your email/password/personal data in being hacked over the next few hours (especially things like forums).
- As a result of the above, a massive wave of phishing attempts.
- Corporates/Admins panicking and turning off services as a precautionary measure over the next hours or days.
thombles | 12 hours ago
sparkling | 12 hours ago
Gigachad | 12 hours ago
jacquesm | 12 hours ago
What else do you expect them to do? Pray?
Switching something off is far preferably over being hacked.
nr378 | 12 hours ago
juliusjh | 12 hours ago
echelon | 11 hours ago
We don't really need it anymore now that we have LLMs.
owenthejumper | 11 hours ago
echelon | 11 hours ago
Nobody needs to write any of this code anymore.
Rust is literally the best positioned language to handle the upcoming onslaught of CVEs.
traceroute66 | 10 hours ago
Rust is also a language with no real stdlib, and so you have to import crates for everything including the kitchen sink.
Which opens you up to the very real risk of supply chain vulnerabilities unless you make an active effort to code review your imports and keep the length of your import list under control.[1][2][3]
Rust supporters also need to urgently realise that memory safe != secure. It is very much possible to have vulnerabilities in memory safe code.
This has been demonstrated by Cloudflare[4] and countless others.
Age-old vulnerability classes such as input validation, error handling and many others are still very much possible in a Rust codebase.
So please. Yes, I'm sure Rust is a fantastic memory-safe language. But do not portray it as being magically immune from CVEs.
[1] https://kerkour.com/rust-supply-chain-nightmare
[2] https://tweedegolf.nl/en/blog/119/sudo-rs-depencencies-when-...
[3] https://tweedegolf.nl/en/blog/104/dealing-with-dependencies-...
[4] https://hackaday.com/2025/11/20/how-one-uncaught-rust-except...
bombcar | 9 hours ago
Well-architected solutions would have the static part broken out so only the dynamic content is on a separate domain/host and that part can be secured as needed. Then something like this only turns off your forms/upload dialogs.
berkes | 9 hours ago
traceroute66 | 9 hours ago
I'm not rising to that bait. I'm sure you know perfectly well what I mean.
So let's just be polite, cordial and leave that topic there there. I'm sure you know its a topic that attracts 'strong views', particularly from the Rust side, which is no doubt why you're trying to engage on it.
berkes | 9 hours ago
The only times I had to use third party packages for basic stuff, was when developing embedded software on limited hardware.
Do you mean that for async we need third party runtimes like tokyo? Or that types and utilities that many other languages ship by default in stdlib, like http aren't in rusts?
I'm sorry for the tone of my post. It was meant as honest surprise, but I clearly see now how it sounds baity and provoking.
skydhash | 8 hours ago
https://github.com/casey/just/blob/master/Cargo.lock
And the helix editor
https://github.com/helix-editor/helix/blob/master/Cargo.lock
Compare them to the dependencies of gnu make (pretty sure it’s only posix)
https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/m...
And vim
https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/c...
###
Downloading the internet to build a smallish software is always bad in my opinion.
sgarland | 8 hours ago
In contrast (I know this is apples to oranges), Python’s stdlib is incredibly broad. colorsys lets you convert between color spaces. plistlib lets you read and write Apple’s property list files. graphlib has a topological sorter, which can lead to hilariously short interview questions when the interviewer isn’t familiar with Python’s stdlib.
ndriscoll | 8 hours ago
kllrnohj | 10 hours ago
PHP still powers approximately 70% of websites
1718627440 | 9 hours ago
amiga386 | 8 hours ago
I don't have a problem with it.
govulncheck tells me if my codebase is actually affected by CVEs or not. So if there's 50 CVE'd modules but my codebase doesn't use them, I sleep.
Secondly, the fix is almost always "go get -u <affected module>", and because it's a CVE, it's usually just a bugfix release and still completely compatible with how I'm using it... but I run the test suite to be more certain.
bilekas | 11 hours ago
juliusjh | 10 hours ago
1) It is now much easier to work in a language with better security features such as Rust. Previously, there definitely was some kind of trade-off between accessibility, performance, and security, and some people argue that this is over. I don't know if this is true, but it seems plausible.
2) You can now translate your legacy projects to a different language much more easily. This is definitely true, but that doesn't mean it doesn't introduce new/other problems or that it is easy enough (again, I simply don't know).
echelon | 9 hours ago
rossvor | 8 hours ago
b112 | 9 hours ago
If you don't understand the language(eg, not easy to work with), don't work professionally in it. All LLM work need audit, a second set of eyes, just as work from a coworker needs peer review prior to sign off.
How can one peer review an LLM without full, experienced knowledge?
gregoriol | 9 hours ago
echelon | 9 hours ago
TacticalCoder | 13 hours ago
Can we discuss that at least a tiny bit?
How do people feel about running servers with PHP today?
Good4boothee | 12 hours ago
qwm | 10 hours ago
qwm | 11 hours ago
echoangle | 8 hours ago
piker | 13 hours ago
72deluxe | 12 hours ago
nananana9 | 10 hours ago
wccrawford | 8 hours ago
This looks like one of those things.
Tepix | 11 hours ago
cubefox | 13 hours ago
lioeters | 12 hours ago
cubefox | 9 hours ago
alper | 13 hours ago
No excuse whatsoever to not either rewrite your website of PHP or to rewrite PHP itself to Rust.
TekMol | 12 hours ago
But it is not clear if releasing the fix early would make the damage smaller or larger.
Having the patch probably makes creating an exploit easier. So the number of attacks would increase.
There is no way to coordinate the whole world on an earlier time. I would guess the number of people who have to patch their instances is in the hundreds of thousands.
Everybody who actively watches the topic already has the option to shut down their instances.
So ringing the bell and getting as many people as possible to shut down their webservers now and patch at 14:00 might be the best in terms of damage minimisation.
By the way, it is not enough to just "shutdown -h now" and then later restart and "apt update && apt upgrade". The moment the machine comes back, it can get hacked. So you should make sure the webserver does not start after the next boot. For Apache this would be something like "rm /etc/systemd/system/multi-user.target.wants/apache2.service" and then after patching recreate the symlink via something like "ln -s /lib/systemd/system/apache2.service /etc/systemd/system/multi-user.target.wants/apache2.service".
fredsted | 12 hours ago
If not, you or our agent could build an exploit from the information that's already out.
TekMol | 12 hours ago
It seems the published exploit can be easily prevented by filtering out multipart post requests. So people actively watching the situation can already prevent that issue by filtering those.
cinpol | 12 hours ago
system2 | 12 hours ago
rtuin | 12 hours ago
system2 | 12 hours ago
These two seem to do the trick, but again I am not 1000% sure until tomorrow morning's deeper dive. My eyes are burning, and I can't sleep because of the stress this exploit.
Macuyiko | 12 hours ago
@multipart header_regexp Content-Type (?i)multipart respond @multipart 403
@uploads_php path_regexp uploads_php ^/(?:./)?wp-content/uploads/.\.php(?:/.*)?respond @uploads_php 404
Plus the php.ini changes, "session.upload_progress.enabled = Off" and strict mode. Let's hope it holds until then
bombcar | 11 hours ago
dmsch | 12 hours ago
AndroTux | 12 hours ago
In theory. In practice, many can't just decide to shut down their service for a few hours.
Gigachad | 11 hours ago
yreg | 10 hours ago
WP sites like whitehouse.gov, TechCrunch, Time?
I don't see anything well known being down.
Shank | 10 hours ago
ganzsz | 10 hours ago
Gigachad | 10 hours ago
tux3 | 10 hours ago
This leaked yesterday in part because so many people had advance notice.
mx7zysuj4xew | 9 hours ago
An exploit can only "leak" if it's a private 0day used by APTs.
When warnings are sent out it has already been a public fact. Keeping some kind of dumbass embargo is just pointless theatre
crote | 9 hours ago
Boom. A leak. It's now a public fact, so we'll instantly see people exploiting it, right? Except that without a commit or patch fixing it, or even a suggestion of a workaround, you are searching for a needle in a haystack. It could be literally anywhere, after all!
In fact, it is so well-hidden that I have not even discovered it myself yet. But its presence is a statistical certainty due to the sheer size of the codebase, so we should assume it is somewhere in there. Did I just doom every W11 user, or are perhaps embargoes at least somewhat useful?
mx7zysuj4xew | 3 hours ago
> I feel like all "non-inner-circle people" here are taken for a laugh. OpenAI and these security companies sat on this for 2 months, decided for themselves who gets access to an early fix, and then leave the rest out to dry
Had they just kept this between themselves and the vendor this would've been effective.
Instead they selectively released it to various parties one of which promptly leaked it.
This is exactly what should have been expected
Either it's 100% silent or it's out there
thinkingtoilet | 10 hours ago
nkozyra | 9 hours ago
xena | 9 hours ago
nubinetwork | 9 hours ago
How does a mobile game use PHP? Wouldn't the game code use a custom socket and protocol for its comms?
gyaru | 9 hours ago
nubinetwork | 8 hours ago
shevy-java | 12 hours ago
No matter the excuse, the security issue must be fixed. Anyone trying to delay this is not acting in good faith. I understand your rationale but that does not excuse you from being labelled as such too.
We should live in the age of open source AT ALL TIMES. No exceptions, for anyone, no matter the reasons. And that includes those who want to withhold code or patches.
yreg | 10 hours ago
luckylion | 9 hours ago
A lot of people are going to do the math on migrating. Bugs happen everywhere. Leaving the community out in the cold and only supplying the corporate sponsors doesn't.
joshuat | 11 hours ago
https://images.chainguard.dev/directory/image/php/versions
pxtail | 11 hours ago
windowsworkstoo | 11 hours ago
jsploit | 9 hours ago
kassner | 10 hours ago
ibejoeb | 8 hours ago
nightbun | 9 hours ago
AznHisoka | 9 hours ago
snitch182 | 9 hours ago
crote | 9 hours ago
philipwhiuk | 8 hours ago
UncleMeat | 9 hours ago
I think that this made sense a few years ago but in today's world it is so feasible to give an LLM a hint and throw some cash at it to find an exploit that I don't think this calculus makes sense anymore.
kalaksi | 9 hours ago
damsta | 12 hours ago
Gigachad | 12 hours ago
BoppreH | 12 hours ago
AlexITC | 12 hours ago
qtqtqt | 12 hours ago
rmccue | 10 hours ago
reddalo | 12 hours ago
[original: The Release Candidate for the patched version is out!]
https://hub.docker.com/_/php/tags?name=8.5
tmstieff | 12 hours ago
azeirah | 12 hours ago
azeirah | 12 hours ago
8.5.12RC1 is a planned RC, see: https://discourse.thephp.foundation/t/php-php-8-5-12rc1-avai...
petervandijck | 12 hours ago
reddalo | 12 hours ago
basilikum | 12 hours ago
If not I suggest PHenomenalPhail.
cubefox | 9 hours ago
shevy-java | 12 hours ago
Why?
Because some upstream services here in central Europe, are closed down because of that PHP problem. So now I am annoyed since this disrupted my workflow.
PHP, please either get your act together - or disband.
chrisvenum | 12 hours ago
Can’t find any reliable information on what to do prior to the patch, seen some info that turning off session progress does not mitigate.
Anyway.. back to calling everyone
[OP] xd | 11 hours ago
bombcar | 10 hours ago
gregoriol | 9 hours ago
compass_copium | 9 hours ago
bombcar | 8 hours ago
After all this is done, CERT-EU isn't going to write the defense of your actions for you.
compass_copium | 9 hours ago
bombcar | 8 hours ago
"X may mitigate some of the active attacks" is helpful - you can evaluate if X impacts you, and make a choice.
"Y is how we're seeing the attacks" is helpful - you can setup logging to see if you're being exploited.
"Z reduces but we can't say it eliminates the risk" is similar.
"SHUT IT ALL DOWN" doesn't do much but make good noise and increase the chance that the next one is considered to be a "boy-crying-wolf" scenario.
(Of course, taking all dev/test/unimportant sites down for a few hours is painless, but Wordpress/PHP runs some of the biggest sites in the world.)
hobofan | 7 hours ago
Since you wrote your comment the official blog posts describing what exactly is the in the exploit have been released, and "shut it all down" was definitely the right advice to give.
richardbarosky | 11 hours ago
I initially updated the following php.ini setting and verified that it updated via phpinfo(). I understand this to be only a possible mitigation (see below).
According to someone stating they are one of the PHP release managers: https://www.reddit.com/r/PHP/comments/1xb2utu/comment/phyu5m...I use Apache, and added an htaccess rewrite rule in my base directory to block all requests containing multi-part headers. Rewrite rules can also be added into Apache virtual host blocks. Accepting file uploads are not a critical function of the app in my case. This blocks multi-part form requests before they reach PHP.
And verified the non-block vs. block case. https://freeimage.host/i/nOqumyNI'm continuing to learn about the situation and may take the server offline as I learn more.
The writeup I found here:
https://jackalsyn.com/posts/php-up-2026.html
Content from a couple of my ChatGPT 6 Pro sessions about the issue:
https://chatgpt.com/share/6ad89ea3-b2f0-83ea-9c4c-2ecf5cc24b...
https://chatgpt.com/share/6ad8ad3d-3f6c-83e9-abf0-41da8a0d65...
https://en.wikipedia.org/wiki/PHP2Shellgiancarlostoro | 11 hours ago
cube00 | 10 hours ago
Users on the Free plan have access to the Cloudflare Free Managed Ruleset, a subset of the Cloudflare Managed Ruleset.
https://developers.cloudflare.com/waf/get-started/
giancarlostoro | 6 hours ago
Everything else I use is not on PHP.
bombcar | 10 hours ago
zo9yhylnu | 10 hours ago
This suggests they might not have been exploits related to the CVE in question, so what you did might not be enough, be careful.
nicce | 10 hours ago
tikotus | 9 hours ago
nr378 | 9 hours ago
huhtenberg | 8 hours ago
Add this to nginx.conf (or drop as a text file into /etc/nginx/conf.d/) :
Then in every 'location /' block for every hosted server: Then restart nginx.deepersprout | 11 hours ago
moebrowne | 11 hours ago
dstu | 10 hours ago
00deadbeef | 10 hours ago
mlekoszek | 11 hours ago
rekl | 11 hours ago
hk__2 | 11 hours ago
Deukhoofd | 10 hours ago
asimovDev | 8 hours ago
AdamGibbins | 8 hours ago
Avamander | 10 hours ago
I think this one more great example what kind of a liability and ticking time-bomb memory-unsafe code is.
panzi | 10 hours ago
yread | 10 hours ago
pezgordo | 10 hours ago
biinjo | 10 hours ago
Seriously though. I don’t know what’s best. Taking everything down or not.. I just run a small time SaaS.
liquidfood | 10 hours ago
Shank | 10 hours ago
bombcar | 10 hours ago
berkes | 9 hours ago
And the work to clean up if you get compromised is massive.
tosti | 9 hours ago
500mazaire | 9 hours ago
vbezhenar | 8 hours ago
500mazaire | 8 hours ago
klhs | 9 hours ago
Edit: Or maybe not? At least one service on their IT-department's list seems to be working again. :-)
andix | 8 hours ago
fock | 7 hours ago
andix | 7 hours ago
airtnp | 10 hours ago
I wonder if this is the new norm for LLM era...
lpapez | 10 hours ago
mono442 | 10 hours ago
lpapez | 10 hours ago
mono442 | 10 hours ago
anonymous908213 | 10 hours ago
edelbitter | 9 hours ago
tredre3 | 4 hours ago
quotemstr | 10 hours ago
Liftyee | 10 hours ago
1718627440 | 9 hours ago
shikck200 | 10 hours ago
sourcecodeplz | 10 hours ago
https://gist.github.com/SourceCodeplz/82f07c94ca7aa036875622...
relaxatorium | 9 hours ago
m3nu | 9 hours ago
gwillem | 9 hours ago
berkes | 9 hours ago
Many modern hosts run php in fcgi mode, where your app is a process that listens on some http port. And where the webserver is "just" a proxy and ssl termination. Shutting down the process is enough.
But traditionally, php was a module loaded into apache. Where apache not only handled ssl, http etc, but also compiled and ran php for you. With that setup, adding an html file, will keep the php runtime and app online.
edelbitter | 9 hours ago
e.g. if your site usually responds blank for https://site.example/database-passwords-and-other-goodies.ph... but under maintenance mode publishes the configuration verbatim, that would be quickly picked up the usual scanner bots.
hakube | 9 hours ago
dhx | 9 hours ago
The single biggest problem I came across over a decade ago when maintaining an open source PHP web application was web applications at the time typically having access to a common database server role (often also common between users and administrators) which allowed a web application process to read and sometimes write to the entire database. No use of user-specific roles in database servers and row-level-security/column-level-security authorisation. At the time I don't think PostgreSQL even had row-level-security support built into it. A runaway PHP process could return the entire database to the attacker, or change every single row of data held within the database.
The second biggest and related problem was web applications accepting files uploaded from users, or having to generate reports (maybe with external software) and save them to disk for a user to download, and not being able to ensure a runaway PHP process can't just dump all of those files or reports to an attacker. You might have been able to store the user files (or at least a decryption key for the files) in a database but then you're back to dealing with problem (1) above.
Even a decade ago it was fairly common for web application developers (of the PHP sorts too) to be well aware of the need to make their web root read-only, put the web application source code into a read-only directory outside the web root, execute interpreters such as PHP with "nobody"-like permissions, launch a new interpreter process for each connection (not multiple threads within the same process), firewall off the server the web application sits on so a runaway PHP process can't connect to internal servers, etc. Outside of an attacker messing with a database, most other aspects of PHP web applications at the time were immutable if the web application developer / system administrator had setup the environment correctly.
Is there a solution for (1) and (2) for PHP web application development that has become popular in the proceeding decade?
edit: also nominating the shared $_SESSION state of PHP that was typical a decade ago to just be left to default (e.g. all PHP processes just read/write session files to a common /tmp directory). https://www.php.net/manual/en/function.session-set-save-hand... should probably instead be used by web application developers to somehow better isolate session state between users.
dwedge | 8 hours ago
A dynamic language having access to all of the files it has access to is not unique to PHP. Vulnerabilities are not unique to PHP, and I doubt the Dutch National Cyber Security Center took their website offline because they lack user-specific roles in the database: https://www.ncsc.nl/index-en.html
So maybe save your elitism for a day when so many of us aren't already putting out fires? Congratulations on not being part of the 75% of the internet affected.
cimi_ | 8 hours ago
tossstone | 8 hours ago
dhx | 4 hours ago
The question to ask is should these defaults be tightened. For example, disallow read and execution of anything outside /var/www/, such as /usr/bin/sh. For example, block syscalls PHP won't ever use to limit chance of a compromised PHP process being able to utilise a LPE kernel vulnerability. And then update user installation documentation to explain the onus is on the user to open up very restrictive default permissions should they really have a need to do so.
[1] https://www.freedesktop.org/software/systemd/man/latest/syst...
fock | 8 hours ago
nr378 | 8 hours ago
dhx | 4 hours ago
Vulnerable but perhaps with no impact. If you've setup your web server well, the vulnerable PHP process is sandboxed, at least to some degree, and an attacker executing their own code within the compromised PHP process can't move laterally through your internal networks, write files to disk, read files from disk, etc because you've locked down the PHP process.
In 2026, perhaps it's possible to:
1. Use systemd socket activation with Accept=yes [1] and strict sandboxing applied to a systemd service that executes the PHP interpreter. The result being each incoming request is dealt with inside an isolated PHP process spawned specifically to handle the request. Compromise of a PHP process doesn't impact any other concurrent requests, or any future requests, except through defined sandbox interfaces such as access to a database server socket.
2. For each user of the web application (perhaps including an 'anonymous' user too if anonymous users have access to dynamic content), if using PostgreSQL, create a role in PostgreSQL for each web application user. Then use row-level-security permissions and security barrier views within the database, and have the PHP process accept credentials from the user which are then needed to be passed through to PostgreSQL to login as that individual user.
It's not without some significant downsides:
1. It's complex and you might be the only person in the world trying to use PHP in this secure way. And if you're going this far, for a complex web application, it'd be best to split it into smaller web applications each with their own systemd service defining specific sandboxing constraints. E.g. microservice architecture where "login", "file upload", "user administration" are all separated with different sandboxing constraints applied to each.
2. Performance will suffer and you'll need more resources--for spawning new PHP processes from scratch for each request (although this is already the case with php-fpm which is most widely used), and for dealing with row-level-security in PostgreSQL (see e.g. LEAKPROOF functions).
The more common pattern I've come across on public websites in recent times that might mirror some of the above is client-side JavaScript dynamic rendering with API calls to a GraphQL database exposed on the Internet (using e.g. field-level access control). The user isolation problem is essentially pushed from PHP+PostgreSQL to a GraphQL implementation.
[1] https://www.freedesktop.org/software/systemd/man/latest/syst...
hn_submit | 8 hours ago
I even have a preference for web stores which use ASP.NET or Java since I know my personal information are safe there.
There are probably thousands of web stores using PHP unwittingly too. I've noticed only about half of them have been taken offline.
yyyk | 5 hours ago
The one gripe I'll have is that rowlevel security is slow and messy to use. If a design allows skipping it, it should be skipped.
cojocarudavid | 8 hours ago
Perz1val | 5 hours ago
codethief | 8 hours ago
pier25 | 8 hours ago
tikotus | 8 hours ago
nananana9 | 8 hours ago
Bengalilol | 8 hours ago
shevy-java | 8 hours ago
We need a long-term solution with regards to PHP. PHP is a success story - so much web-software depends on it. But it also has become a liability when they are all now scared that the server can be easily taken over. This is not acceptable, PHP.
hn_submit | 7 hours ago
Even though there are much more secure CMS technologies out there like Umbraco or Piranha (both ASP.NET) and web stores like NopCommerce (ASP.NET also).
There are just too many technically clueless people building web sites and web stores.
TZubiri | 8 hours ago
Anyone have an archive link?
klausa | 8 hours ago
normis | 8 hours ago
akileos | 8 hours ago
https://www.php.net/downloads.php?source=Y
It's really up.
mjmas | 8 hours ago
chrismonsanto | 8 hours ago
kalleboo | 8 hours ago
mgrandl | 7 hours ago
wink | 7 hours ago
mgrandl | 7 hours ago
qwm | 7 hours ago
linobino1 | 6 hours ago
OtherShrezzing | 8 hours ago
I get that maintenance teams need to have conviction in this approach, but this is definitely going to cause catastrophically large data breaches downstream.
ndiddy | 8 hours ago
> Given the severity of these vulnerabilities, the PHP security team provided minimal source-backports for PHP 7.4, PHP 8.0, and PHP 8.1 to help people building from source or without access to an LTS vendor.
airtnp | 8 hours ago
edelbitter | 7 hours ago
Shank | 8 hours ago
kps | 6 hours ago
nr378 | 8 hours ago
https://www.php.net/archive/2026.php#2026-10-21-5
RCE via OOM corruption - https://github.com/php/php-src/security/advisories/GHSA-w8hw...
RCE via stale global state - https://github.com/php/php-src/security/advisories/GHSA-6wmf...
codethief | 7 hours ago
whycome | 7 hours ago
There are so many keeping old php versions alive for compatibility with whatever software
szopin | 7 hours ago
jeremyt | 7 hours ago
kassner | 6 hours ago
ljm | 6 hours ago
There's a lot of zombie software on the net that is ripe for the picking. More food for the botnet.
Wordpress in particular is a stupidly simple vector.
ashkankiani | 6 hours ago
I can't think of a faster way to clear out the vulnerable surface area.
ishouldbework | 4 hours ago
ashkankiani | 4 hours ago
zepearl | 7 hours ago
(I just ran an "emerge --sync" but the mirror that was used does not have yet the updates)
wiredfool | 6 hours ago
https://ubuntu.com/security/CVE-2026-109618
elyobo | 7 hours ago
dvdkon | 7 hours ago
It seems to have a few more technical details.
headinthesky | 6 hours ago
Still waiting on container updates and package updates. Not a peep from cpanel or plesk. What a mess
00deadbeef | 5 hours ago
headinthesky | 4 hours ago
jamietanna | 6 hours ago
linobino1 | 6 hours ago
drrotmos | 5 hours ago
linobino1 | 5 hours ago
Docker hub shows the new tags but the manifests are missing https://hub.docker.com/_/php
1over137 | 5 hours ago
tossstone | 8 hours ago
imzadi | 7 hours ago
So far, I have checked to see if any new files have been placed in our directories or if there have been any file changes. I've also looked at the access logs for unexpected POST requests.
Are there any other steps?
edelbitter | 7 hours ago
hakube | 7 hours ago
codedokode | 7 hours ago
First, there is a huge function, that is hard to read and reason about. Second, instead of proper parsing of "Content-Type" header to extract "boundary" parameter, there is just a set of substring searches which is not correct. It doesn't mean there is a vulnerability but it means PHP can read the header in a way different from a standard-compliant implementation (such as web server, WAF etc).
[1] https://github.com/php/php-src/blob/master/main/rfc1867.c#L7...
edelbitter | 7 hours ago
ChrisArchitect | 7 hours ago
https://news.ycombinator.com/item?id=50176077
https://news.ycombinator.com/item?id=50180836
spenvo | 7 hours ago
bobatsomecompan | 7 hours ago
ashkankiani | 4 hours ago
universa1 | 3 hours ago
https://fedi.katze.sh/@elise/117479383739450605