pics or it didn't happen
You asserted without evidence that there is working examples.
Someone asked for those examples, and instead of providing them, you insulted everyone.
I don't think anybody is asking for the code, but it would be nice to see the claims of working exploits that you're referring to.
A claim can be worth a lot, depending on who is making it and in what context.
If you claim only ancient LAMP boxes are vulnerable, then that's like me saying your "your 80 year old grandma is more prone to accidents".
CVE-2026-109619 is the main memory related vulnerability but it alone isn't enough to break OS level ASLR unless you spam it (brute forcing).
History proves that new technology makes people twitchy in every direction. My anecdotal memory of X-rays is entertaining (we can use them to beam knowledge into brains!) and apocalyptic (X-ray guns will make warfare terrible!).
I have a rule for everything: the information is valid in inverse proportion to its political value. This is a bad exploit, and it happens from time to time. There's also an IPO connected to AI that is very political for many people who threw a lot of money at it.
I also think people want to check it with a vanilla install, not with "poorly configured servers" etc.
I've seen a bit too much (early on, ive not checked anything in the last 12 hours) saying "exploit confirmed", no one is disputing that, just its efficacy - specially after the hype and vanity sites.
However, that still doesn't actually show that the original post is wrong - since we can't actually see how it can be exploited against a vanilla PHP server.
No idea of course if this meets the authors' "out of the box" condition. Who runs a fully stock PHP config?
And I'm usually unpleasantly surprised, but I can deal with it, I know most developers don't have the knowledge to deeply understand if something is really really bad or just a small problem. But now I'm finally at a point where I wonder if people will ever understand. We have critical vulnerabilities in widely used software coming out every other day, we get exploits for (on a technical level) very hard to exploit vulnerabilities in record speed, and yet non-security people still spout "full weaponized PoC or it isn't real" like it's 1999 (not that I was old enough to know that was happening at the time).
I don't understand why nobody believes that security people might know a thing or two. Is it just that it's so much more convenient to close your eyes and pretend that nothing is wrong? I wonder what needs to happen to allow us all to finally have a conversation about how we can make sure that the software that runs all aspects of our life gets more secure.
PHP were right to make the warning so strict, and people were right to take sites down in precaution. It certainly could have been horrific.
However, OpenAI makes it a boy who cried wolf situation and I've no idea if "we expect to see exploits 15 minutes after the patch is launched" was a genuine concern that thankfully doesn't seem to have happened or them trying to over-state the ability of their models.
Your point is valid about how we need to be more concerned about this stuff, but I just wish it wasn't being played for bragging rights by AI guys. I mean, they had an official php2shell website ready-to-go for the patch launch party, which doesn't help it not look like a PR exercise.
There is a wolf in the boy who cried wolf.
Mixing security with PR just does not seem a good idea, and a worrying precedent.
PHP handled it correctly, and I trust them. I don't feel the same about OpenAI.
You can have more than one conversation in a thread, and not everything has to be black-or-white!
https://openai.com/index/patch-the-planet/ https://www.theinformation.com/articles/openai-early-talks-b...
I personally also found the level of marketing noise on some of the websites distasteful for an extremely serious vulnerability of this caliber. I agree that probably didn't help with credibility for readers without any security knowledge.
That being said, the writeups and demos published on these sites made it very clear to anyone with basic knowledge about how things like UAFs get exploited (and I mean basic, I couldn't write a working exploit for something like this myself!) that this is a very serious issue. The presented facts lined up with the claimed impact, unlike the many hallucinated slop repos that appeared before the public disclosure. My issue is that for some reason non-security people often don't believe the security people in cases like these, and I don't quite understand why that is such a consistent issue. And besides, as you already mentioned, it wasn't just OpenAI, Wiz, Calif saying that this was bad, the PHP people said the same. They certainly had no interest in blowing this out of proportion.
I also personally think the concerns about 15 minute exploits were genuine and warranted. Maybe the chance for that wasn't overwhelming, but I believe it was there. The bigger issue, however, comes from the ability of adapting an exploit to other builds once one exists. Another comment on this post asserts this vulnerability "will never be a one-size-fits-all-PWN-button". And historically this has been somewhat true for binary exploitation (depending on your threat model). But the problem is, even if public LLMs can't quite consistently one-shot a full pwn exploit in 15 minutes, they absolutely can very easily adapt an existing exploit to other target versions and builds.
Because that is the criticism here.
And so far, even after the patch is out, it has been impossible for the public to confirm what sort of configurations actually would have been and would not have been vulnerable.
IMHO that is fair criticism.
In retrospect, that seems ill-advised. If you sat behind Cloudflare you were protected from theoretical attacks even before the announcement was made. Obv, hindsight is 20 / 20, but as usual, stuff announced by the AI hype machine does not stand up to scrutiny.
I don't really understand the intent behind a post like this. Sure, this is a harder vulnerability to exploit than Log4Shell. Everything is harder to exploit than Log4Shell. How, exactly, is that meant to weigh on people's decisionmaking?
For the first time, I think, in my whole career, I saw sites yesterday go down instead of trying to mitigate an unpatchable critical vulnerability. They took the availability hit rather than putting their users at risk. Finally. What purpose is served by trying to dial back the concern?
If this was a long nerdy post about exploitability, I'd get it. But it's not. It's essentially a high-level comparison of logic vulnerabilities to memory corruption vulnerabilities. What is this argument for?