In short: The PHP team has fixed 17 security vulnerabilities. Seven are rated critical, and five could even let attackers run their own code. The good news: the critical flaws can only be exploited under certain conditions, not on a default installation. You should update anyway. The safe versions are PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13.
What happened
Four weeks after the stir around the “PHP2Shell” flaws, the next important PHP release is out. It is part of the monthly PHP updates, not an emergency patch. According to heise, four version branches receive updates. Golem sums it up: no need to panic, but admins should get ready.
The five flaws with possible code execution (each CVSS 9.2, “critical”) and their preconditions:
- CVE-2026-129289: Affects PHP-FPM and LSAPI when
FCGI_KEEP_CONN=1is set (the default is 0). A connection is then not cleaned up properly before the next request arrives. A script must also accept input viaphp://input. - CVE-2026-115560: Affects the “session upload progress” feature. Attackers can write data into the session in one format that is later read in another. Precondition: a script sets the session handler to
phpbefore starting the session, and upload progress is enabled. - CVE-2026-129496: A memory bug in the time zone data cache. It can crash PHP; code execution has so far only been shown with protections such as ASLR bypassed.
- CVE-2026-129474: PHP 8.5 and later only. An unauthenticated attacker can run code with a crafted request if
fatal_error_backtraces=1andzend.exception_ignore_args=0are set. - CVE-2026-129182: A bug the developers found while following up on PHP2Shell. Only exploitable with specific settings, among others around
zlib.output_compression.
On top of that there are two more critical flaws (CVE-2026-126714 and CVE-2026-129481) and ten rated high or medium.
Who is affected
- Your own VPS or root server with PHP: yes, please update. Even if your settings don't hit the critical cases, the update closes the other flaws.
- PHP 8.1 or older: going by the version numbers above, these versions get no fixes. Move to 8.2 or newer as soon as your application supports it.
- Web hosting with us: see below, you don't need to install anything.
What you should do now
- Check the version:
php -v. If it is below 8.2.36, 8.3.37, 8.4.28 or 8.5.13 respectively, an update is due. - Update:
apt update && apt upgrade(Debian/Ubuntu, also with the sury.org repository) ordnf upgrade 'php*'(Rocky, AlmaLinux). According to heise, Debian 13 already ships8.4.28-1~deb13u1. Distributions often backport fixes into their own package version; your distribution's security advisory is what counts. - Restart PHP-FPM: for example
systemctl restart php8.3-fpm. Without a restart the old code keeps running. - Check your settings until the update is in:
php -i | grep -E 'session.upload_progress.enabled|fatal_error_backtraces|exception_ignore_args'. If you run nginx withfastcgi_keep_conn on;in front of PHP-FPM, that setsFCGI_KEEP_CONN. The update is still the safer route.
What we at NexoraHost say
For web hosting (Plesk), we take care of the PHP updates on the servers; you don't need to install anything. In Plesk you only choose the PHP version for your website. If you still use 8.1 or older there, switch to a current version now.
On your VPS and root servers you are the admin. We don't install updates there without asking, because that could interrupt your services. If something breaks after the update or you are unsure: open a ticket.
Web hosting → · VPS · Root server Linux · PHP versions in Plesk · Source: heise · Golem
More blog articles
In short: nginx has two critical vulnerabilities nicknamed “nginx2root” (CVE-2026-123007 and CVE-2026-123633). They let attackers run code on the web server without logging in. Almost every nginx version from the last ten years is affected, but only when HTTP/2 is enabled. T...
In short: Apache's HTTP/2 module has a critical vulnerability (CVE-2026-119618). An unauthenticated attacker can use it to run code on the server with the privileges of the web server process. Versions 2.4.55 to 2.4.70 are affected, but only when HTTP/2 is enabled. A fix is...
Short version: On 8 September 2026 Microsoft shipped the largest Patch Tuesday so far – about 974 CVEs, including two actively exploited zero-days and several critical bugs in Remote Desktop (RDP). If you run a Windows V-Server or root server, update today and reboot. Not “s...