PHP2Shell and PwnEscape vulnerabilities: what you need to know
Published on 22 October 2026
Two critical security vulnerabilities were disclosed in recent days: PHP2Shell, which affects PHP, and PwnEscape, which affects KVM hypervisors on Linux. Here is what they mean for your UP-NETWORK services and what you need to do.
PHP2Shell: two critical vulnerabilities in PHP
On 21 October 2026, the PHP project released fixes for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, known together as PHP2Shell. Both are rated 9.2 out of 10 (CVSS v4).
They can allow an attacker to execute code remotely on the server, without authentication, with the privileges of the PHP process. Every PHP installation that serves web pages is affected, whatever the execution mode: PHP-FPM, Apache mod_php, php-cgi or LiteSpeed.
The fixed versions are PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. The PHP project also released fixes for the 7.4, 8.0 and 8.1 branches, which are normally no longer maintained.
Researchers have developed a working exploit, and it is expected to be published soon. We recommend updating without delay.
What we have done
On our Plesk web hosting, the fixed PHP versions (8.2.35, 8.3.36, 8.4.27 and 8.5.12) were installed on 21 October 2026, the day they were released, thanks to the platform’s automatic updates.
All hosted websites use a fixed PHP version, and older PHP versions are no longer offered. Your websites are protected and you have nothing to do.
What you need to do on a VPS or dedicated server
On a VPS or dedicated server, you manage the system and the installed software yourself, including PHP. UP-NETWORK does not work directly on these servers. If you run PHP there, for example for WordPress, Laravel or a control panel such as Plesk or cPanel:
Check your PHP version.
Install the security updates from your distribution or control panel.
Restart PHP-FPM or your web server.
All the steps are described in the guide Update PHP and the Linux kernel.
PwnEscape: an isolation flaw in KVM
The CVE-2026-99999 vulnerability, nicknamed PwnEscape, was published on 15 October 2026 and rated 9.3 out of 10. It lies in the networking code of the Linux kernel, which KVM hypervisors rely on.
A malicious virtual machine could exploit it to break out of its isolation and reach the host server: read its memory, or even execute code on it. The fix has been merged into the Linux kernel and is reaching the distributions (Debian, Ubuntu, RHEL, AlmaLinux, Proxmox…). No real-world exploitation has been reported so far.
Our situation
Our VPS and VDS run on KVM, and our virtualisation platform is among the solutions covered by these security advisories. UP-NETWORK was nevertheless not directly impacted: the way our nodes are connected and the network isolation of our infrastructure greatly reduce the possibilities of exploitation. For security reasons, we do not describe these measures in detail.
You have no action to take on the hypervisor side.
If you run your own hypervisor
If you run your own virtual machines on a dedicated server, for example with Proxmox VE, KVM/libvirt or nested virtualisation, your server is a hypervisor and is directly affected. Update its Linux kernel and then restart it, as explained in the guide.
Need help?
If you have a question about these vulnerabilities or about your service, open a support ticket. If you would rather have us maintain your server, discover our Support and managed services offer.
Sources
The Register: Linux KVM guest-host escape rated critical
TuxCare: PwnEscape