If you liked PHP's last critical vulnerability, you will love PHP's latest critical vulnerability!
https://www.php.net/archive/2026.php#2026-11-18-1
(no, I have no details)
If you liked PHP's last critical vulnerability, you will love PHP's latest critical vulnerability!
https://www.php.net/archive/2026.php#2026-11-18-1
(no, I have no details)
@dnkboston always has been. Complex legacy codebase written in C.
@rysiek I just don't remember seeing so many hair on fire stories about it before last month
@dnkboston the hair on fire stories are relatively recent, industry-wide, and related to new ways generative models are now used to massively speed up vulnerability research.
But also the pretty crap incentives in the vulnerability research business play a part. It is in the best interest of companies doing this sort of work to make hair-on-fire announcements, with logos and branding and whatnot. So, some bugs that would have been quietly fixed with an update are now being played up.
@rysiek My inner cynic is nodding along.
"These releases are part of PHP’s regular four-week release cycle and will address security vulnerabilities affecting all supported PHP versions. The highest severity is CRITICAL.
The issues rated CRITICAL require either non-default configuration or uncommon setups."
@ojs I wonder what they'd use for a CVSS 10 vuln that works in default configuration and without uncommon steps, then
@rysiek "PHP 8.6.0RC7 available". Does that mean "race condition number 7 for version 8.6 available" ?
@rysiek As I heard somewhere:
The S in PHP stands for security.
@rysiek Wow, why is PHP so vulnerable all of a sudden?