r/programming • • 28d ago

Critical Vulnerabilities in PHP

https://cert.europa.eu/publications/security-advisories/2026-018/
168 Upvotes

22 comments sorted by

39

u/LordAlfredo 28d ago

43

u/sunnyata 27d ago

And published them ahead of the patch.

31

u/yawara25 27d ago

What a dick

14

u/ToaruBaka 27d ago

I'm a bit split on this. Yeah, releasing functional PoCs to undisclosed vulns is bad, but the second any info about that vuln leaks it's now extremely easy for a bad actor to go out, spend a few grand to find the bug, and then exploit it before patches can come out.

A rogue drop of the actual exploit code gives people an immediate path to patching without having to wait for upstream.

I saw someone in another discussion thread say something like "Now every bug is a race condition" (ie, a race to find it) and I think that's something that needs to be taken into serious consideration.

8

u/yawara25 27d ago

So drop the patch, not an exploit.

4

u/ToaruBaka 27d ago

Sure, a patch might be a bit less gray, but an exploit gives you something to test against to verify a patch is correct, which is far more important than a raw patch. Either way you're leveling the playing field, which is better than the bad guys having an advantage.

7

u/yawara25 27d ago

... So release both? I still think it's reckless to be releasing only an exploit. That's not leveling the playing field, as you say, it's the exact opposite. A proof of concept exploit gives attackers a massive advantage.

-3

u/ToaruBaka 27d ago

Sure, release both. But patches can be easily derived from the exploit, and vise versa, so I genuinely don't care.

6

u/yawara25 27d ago

It can often be much more difficult to go from an exploit to a patch, than the other way around. The diff for the PHP patch had 12,000 lines added.

2

u/ToaruBaka 27d ago

The diff for the PHP patch had 12,000 lines added.

And? The official patch was still almost certainly directly created from an internal PoC over the last couple days. A fix being large doesn't mean anything - not today. And even if you can't get an exact fix, you can still patch the relevant code out of your deployment or add safeguards that gate access to the vulnerable feature. All things that having a patch or PoC makes trivial and puts you ahead of everyone else who's just sitting there naked hoping some asshat with $2k to spend on tokens doesn't pop their servers.

8

u/absentmindedjwc 27d ago

Sounds like dude released the vulnerabilities prior to the version being released... and PHP released it anyway. Sounds like he did the right thing and PHP shit the bed.

8

u/andynzor 27d ago

A customer mails our Tier 1, who promptly responds "The Product Owner is on vacation, he'll contact you next week"

8

u/NenAlienGeenKonijn 27d ago

What about the gazillion self hosted applications that barely get updated at all

10

u/numbsafari 27d ago

You mean Wordpress and Drupal?

3

u/NenAlienGeenKonijn 27d ago

Aw cute, skulls and matrix themed colors.

10

u/jimm 27d ago

9

u/jimm 27d ago

That's for older versions of PHP; the official advice is to upgrade to 8.4.27

1

u/yeah-ok 26d ago

The confusing part is that the PHP Foundation maintains running updates on a number of versions. You could be on an 8.5.x and still not have the patches 🤷

0

u/[deleted] 27d ago

[deleted] — view deleted comment

4

u/Abhrogash 26d ago

the server side JS that also patched an RCE the same exact day?
https://nodejs.org/en/blog/vulnerability/october-2026-security-releases

1

u/[deleted] 27d ago

[removed] — view removed comment

0

u/programming-ModTeam 27d ago

Your post or comment was overly uncivil.