Upcoming Critical PHP Security Release (18 Nov 2026)
31 points by luke8086
31 points by luke8086
If it happens again next month, I'm setting up a cron job to stop my nextcloud instance every four weeks to match their release cycle.
The tone is my way to cope with the never ending stream of security updates.
First I disabled http2 on nginx, now php8.4-fpm, in between I upgraded my linux kernel due to the network kernel panic CVE - and luckily I had no java exposed. Let me know when I can tell my hoster to just unplug the system, just to be safe.
Given the state of the PHP code base and the way these fixes are rushed, it is likely that the stream of severe vulnerabilities will continue for quite a while. It will be a years long endeavor to make this code base more robust and secure.
Got a source for "the state of the PHP code base"? Not familiar with the internals and would be interested to find out why
Just read the diff for the PHP2Shell fix. This is terrifying. When a patch looks like this, you just know that there are more bugs in the code base.
Quite possible and I wish the best to the PHP team at large (I also wish them proper funding).
"The issues rated CRITICAL require either non-default configuration or uncommon setups."
Love that they added that sentence. Hopefully it's the start of a trend!
It doesn't tell me anything though! Nobody runs a completely default configuration of PHP, there are almost always tweaks to performance stuff or bytecode caching or file size limits or memory usage limits etc etc. And a PHP file can make its own tweaks with the ini_set function.
$ zless /usr/share/doc/php8.4-common/changelog.Debian.gz
php8.4 (8.4.28-1~deb13u1) trixie-security; urgency=high
* New upstream version 8.4.28
+ [CVE-2026-129538] PHP-CGI out-of-bounds read and write during
PATH_INFO correction.
+ [CVE-2026-129496] Timezone cache use-after-free can lead to remote
code execution.
+ [CVE-2026-129289] PHP-FPM request smuggling through an unread HTTP
request body.
+ [CVE-2026-129292] PHP-FPM status endpoint XSS via unescaped user and
script fields.
+ [CVE-2026-129291] PHP-FPM epoll use-after-free can lead to local
privilege escalation.
+ [CVE-2026-128090] PHAR OpenSSL signature bypass via algorithm
downgrade.
+ [CVE-2026-126714] Partially overwritten session files can lead to
remote code execution.
+ [CVE-2026-115560] Session serializer mismatch can lead to remote code
execution.
+ [CVE-2026-15353] SOAP information disclosure through malformed array
dimensions.
+ [CVE-2026-129506] SOAP use-after-free when processing DTD entity
references.
+ [CVE-2026-128064] Mixed-case HTTPS and FTPS URLs can expose data in
plaintext.
+ [CVE-2026-127960] Denial of service through folded HTTP response
headers.
I wonder if this more than just https://www.php.net/archive/2026.php#2026-10-23-1 from October 23:
Since this setup is unlikely in practice, we are handling it in the regular release cycle and will publish a full advisory for CVE-2026-115560 with the next release.
It just never stops lately. It's a new critical CVE weekly. Seems to alternate between a few languages*, just roll 1d6 to see what this week's critically vulnerable language is (any time you roll a 1, roll two more times to get a combo week!)