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.
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.
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.
umbula | 6 hours ago
mjac | 6 hours ago
https://php2php2shell.com/
umbula | 6 hours ago
Joel_Mckay | 6 hours ago
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
0x0 | 6 hours ago
sjs382 | 6 hours ago
r1ch | 5 hours ago
esskay | 6 hours ago
nubinetwork | 6 hours ago
[OP] petecooper | 6 hours ago
mjac | 6 hours ago
https://www.php.net/ChangeLog-8.php#8.2.36
kijin | 5 hours ago
showerst | 6 hours ago
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.
theemathas | 5 hours ago
tyilo | 6 hours ago
Screenshot taken at around 2026-11-18 14:00 UTC.
They seem to have accidentally posted that instead of the fix to nginx.
spiderfarmer | 5 hours ago
So the attack surface is not as large as last time.
zulux | 4 hours ago
phplovesong | 5 hours ago
stronglikedan | 5 hours ago
phplovesong | 5 hours ago
0xdb | 5 hours ago
captn3m0 | 3 hours ago
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...