Requires session.upload_progress.enabled=1 which many people disabled as a mitigation to the earlier CVEs. If you haven't, you should disable it if possible.
"Relevant configurations include nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI applications that retain backend connections, and LSAPI. Standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated PHP-FPM attack."
This one _seems_ to only affect FrankenPHP so far, but could maybe be extended.
This batch requires an immediate patch in case someone gets reliable exploit for those RCEs, but it doesn't appear to be 'take down the websites' level of bad.
The patch level for the version fixed are in the packaging suffix, and not necessarily the program version number.
Checking the deb package release notes, will disclose which CVE are fixed.
Looking at just the 8.5-fpm or Apache mod_php will not indicate the system is still not patched. They both should be fixed as of last week if auto-updates have run.
If more CVE/RCE have dropped (we should expect the next year will have many), than it may take weeks for the patch to propagate across the ecosystem. =3
So this one isn't actually fixed yet it seems. I released my shitpost website prematurely since the draft said it was fixed in 8.5.13. I'd appreciate if you could remove references to it.
pretty sure the vast majority of php sites are using fpm these days, but those still on apache with mod_php need to update, or finally move to nginx/fpm.
For the foreseeable future. I'm treating all updates as immediately mandatory because I assume that, going forward, important security issues won't be discussed as much.
For the criticals:
https://github.com/php/php-src/security/advisories/GHSA-8mjj...
Requires the following php.ini settings -- fatal_error_backtraces=1 and zend.exception_ignore_args=0
zend.exception_ignore_args is 1 by default.
https://github.com/php/php-src/security/advisories/GHSA-gr4f...
Doesn't have a setting mitigation but doesn't seem trivial to set up.
https://github.com/php/php-src/security/advisories/GHSA-gr4f...
Doesn't have a setting mitigation but doesn't seem trivial to set up.
https://github.com/php/php-src/security/advisories/GHSA-658j...
Requires session.upload_progress.enabled=1 which many people disabled as a mitigation to the earlier CVEs. If you haven't, you should disable it if possible.
https://github.com/php/php-src/security/advisories/GHSA-qc49...
"Relevant configurations include nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI applications that retain backend connections, and LSAPI. Standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated PHP-FPM attack."
https://github.com/php/php-src/security/advisories/GHSA-w8hw...
This one _seems_ to only affect FrankenPHP so far, but could maybe be extended.
This batch requires an immediate patch in case someone gets reliable exploit for those RCEs, but it doesn't appear to be 'take down the websites' level of bad.
More complete list of critical vulns at https://github.com/php/php-src/security/advisories?query=sev... (look at the ones that are published today).
Seems like simply.com accidentally broke the embargo yesterday: https://i.postimg.cc/906qZgNM/image-(9).png
Screenshot taken at around 2026-11-18 14:00 UTC.
They seem to have accidentally posted that instead of the fix to nginx.
Source code links (tagged but not currently released):
(I'm using the GitHub releases Atom feed, I'm not breaking any embargoes this time…)
Looking at the 8.2.36 security patch, you can see a list of backported CVEs directly as it doesn't include all the other updates
https://www.php.net/ChangeLog-8.php#8.2.36
The backport changelog is not an exhaustive list. It is missing a couple of use-after-free CVEs that only affect PHP 8.5+.
mbregx, which relies on the unmaintained https://endoflife.date/oniguruma regex engine is now deprecated. It is slated for removal in 9.0: https://wiki.php.net/rfc/eol-oniguruma.
It is the same regex engine that is used/forked by Ruby and underlies the recent spate of CVEs on Ruby/Gitlab etc.
Also used by jq, bat, ghostty. uutils-coreutils recently switched out[1] looks like.
[1]: https://github.com/endoflife-date/endoflife.date/pull/9860#i...
So, how bad is it?
Fixes "Unauthenticated RCE in PHP on Apache + mod_php due to unexpected ErrorDocument reentrancy", still need to review for other criticals
https://php2php2shell.com/
From a quick scan, I don't see anything earth-shattering. Worth you doing your own research, of course.
The patch level for the version fixed are in the packaging suffix, and not necessarily the program version number.
Checking the deb package release notes, will disclose which CVE are fixed.
Looking at just the 8.5-fpm or Apache mod_php will not indicate the system is still not patched. They both should be fixed as of last week if auto-updates have run.
If more CVE/RCE have dropped (we should expect the next year will have many), than it may take weeks for the patch to propagate across the ecosystem. =3
This page just shows a countdown to 2026-12-19, a month from now ?
It's just a countdown that aligns with the next scheduled PHP monthly release.
So this one isn't actually fixed yet it seems. I released my shitpost website prematurely since the draft said it was fixed in 8.5.13. I'd appreciate if you could remove references to it.
pretty sure the vast majority of php sites are using fpm these days, but those still on apache with mod_php need to update, or finally move to nginx/fpm.
Umamusume already shut down, much like the last time.
updated official docker images seem to be published now as well
"The issues rated CRITICAL require either non-default configuration or uncommon setups."
So the attack surface is not as large as last time.
For the foreseeable future. I'm treating all updates as immediately mandatory because I assume that, going forward, important security issues won't be discussed as much.
PHP keeps on giving. Another day, another PHP wart.
Yup, just like literally every other language still in use.
The other ones are mostly sane tho, PHP not so much.