275 points danlark1 1 hour ago 76 comments
pettijohn 1 hour ago | parent
Maxious 1 hour ago | parent
rs999gti 1 hour ago | parent
dd8601fn 1 hour ago | parent
But also I haven’t seen much of that style of bulletin boards in ages. Maybe the occasional EEVBlog or Ars kinda count?
whycome 1 hour ago | parent
phplovesong 15 minutes ago | parent
apocalyptic0n3 58 minutes ago | parent
sehw 1 hour ago | parent
dewey 1 hour ago | parent
dspillett 1 hour ago | parent
tchalla 1 hour ago | parent
evandena 1 hour ago | parent
asbv-1qq 1 hour ago | parent
No compute costs for finding the issue or for writing the exploit are disclosed.
But it is marketed as if it were the first RCE found in human history.
pixl97 58 minutes ago | parent
So yea, it's a big deal.
SoftTalker 44 minutes ago | parent
nope1000 52 minutes ago | parent
pizzafeelsright 44 minutes ago | parent
Everything was sound and every test passed for years along with every security scan because intent was not validated.
I would expect an unending source of exploits in the future until AI rewrites everything.
simonw 1 hour ago | parent
August 19, 2026: Wiz Research discovers the first PHP vulnerability using Wiz Atlas, Gemini 4 Argon, and GPT-5.6 Sol.
August 20, 2026: Unauthenticated RCE is confirmed against Drupal.
August 21, 2026: Unauthenticated RCE is confirmed against WordPress.
August 24, 2026: Wiz Research reports the vulnerabilities to the PHP security team.
September 21, 2026: PHP acknowledges the reports and begins developing a coordinated fix.
October 21, 2026: Patched PHP releases become available.
October 21, 2026: Public disclosure.
I want to understand how it leaked. I guess a whole lot of people were looped in between September 21 and October 21?
projektfu 1 hour ago | parent
bombcar 1 hour ago | parent
mjr00 1 hour ago | parent
Yes. I was at AWS when Spectre and Meltdown were discovered, and we received approximately a month of advance notice and put together teams to apply mitigations. The work of the team was on a need-to-know basis--even team members' managers only knew they were pulled onto a critical project, not what the specific project was. But there were still 30+ people in the company who knew, and that was just one company (I'm guessing Google/Azure/other cloud providers got similar advance notice).
Now, this is a much wider scale vulnerability, in the sense that Spectre/Meltdown primarily impacted cloud providers, but this attack impacts literally anyone who runs PHP. Dozens, if not hundreds, of companies likely got advance notice that a patch needed to be installed. In those companies there are teams of people applying those patches. All it takes is one of them who wants 15 minutes of internet fame to leak the details.
geerlingguy 1 hour ago | parent
The wider the pre-release news spreads, the more chance you get someone who will spill the beans (intentionally or not).
its606 1 hour ago | parent
Good4boothee 1 hour ago | parent
If I understand correctly someone showed off a video of exploit in action - just like the ones included in article - and the visible messages were enough for other LLM users to discover the exploited bug.
simonw 56 minutes ago | parent
Were they already looped in or was it circulating outside of the trusted group already?
Topfi 1 hour ago | parent
Edit: Apparently this had been reported more than half a decade ago [0]. I am getting more confused the more I look into this, hopeful for a well written, factual post-mortem from someone who hasn't actively avoided PHP for the last decade.
phoronixrly 1 hour ago | parent
edh649 1 hour ago | parent
geerlingguy 1 hour ago | parent
mg794613 54 minutes ago | parent
Especially after fumbling it like this.
"Buy our product, because we found a bug", yeah and you leaked it too.
wildmXranat 52 minutes ago | parent
jongjong 52 minutes ago | parent
I suspect it's a matter of time before all mainstream blockchain projects are cracked. Many of those projects are hundreds of thousands of lines of code. There's no way they don't have vulnerabilities given that AI is now uncovering so many vulnerabilities in such high exposure projects.
I was a code minimalist before, now I'm a radical minimalist. We need to get the lines of code down to the absolute minimum.
Attack surfaces need to be clearly defined, enumerable and testable under all possible conditions.
wat10000 46 minutes ago | parent
NooneAtAll3 49 minutes ago | parent
airtnp 48 minutes ago | parent
Wiz (with GPT 5.6 Sol + Gemini 4 Argon) : Remote process-memory disclosure; OPcache type confusion; Fatal-error backtrace UAF. POC on Wordpress, Drupal and Joomla
Calif (with LLM, no specific model, but model is accessible to all): Zend HashTable OOM. Targets PHP-FPM and mod_php.
Both discovers the UAF on upload progress unserializer.
Surprised to see the anime girl dancing with POC is really uploaded by Calif researchers.
airtnp 47 minutes ago | parent
https://github.com/php/php-src/commit/712e60f9edfd03f0960fc4...
processunknown 44 minutes ago | parent
airtnp 39 minutes ago | parent
echoangle 34 minutes ago | parent
echoangle 35 minutes ago | parent
chuckadams 38 minutes ago | parent
wren6991 34 minutes ago | parent
nananana9 27 minutes ago | parent
But be careful, updating packages can be difficult, here's a MD file for you to give the super genius AGI to tell it how to apply it for you.
eptcyka 29 minutes ago | parent
No, scratch that. I should replace it with something that is not a trash fire.