
Notice Links:
| Posted | Thu, 19 Nov 2026 22:35 PM UTC
Thu, 19 Nov 2026 17:35 PM EST |
|---|---|
| Last Update | Thu, 19 Nov 2026 23:09 PM UTC (50 hours ago)
Thu, 19 Nov 2026 18:09 PM EST |
| Status | Open |
Multiple critical security vulnerabilities in PHP have been released, including one known as phpAfterShell. They have been described as critical, with potential to allow an attacker to run malicious code on an affected server without logging in. For details of the posted vulnerabilities, see https://github.com/php/php-src/security/advisories This includes CVE-2026-115560, CVE-2026-129182, CVE-2026-126714, CVE-2026-129289, CVE-2026-129474, CVE-2026-129481, CVE-2026-129496, CVE-2026-129291 PHP powers websites and applications such as WordPress, Moodle and Joomla, as well as parts of hosting panels such as cPanel and Plesk. Updating your website's plugins or application alone does not update the underlying PHP software. Emergency maintenance: proactive security updatesAs an initial response to the vulnerabilities we have a process to install the latest PHP packages available from server's existing package repositories and restart the services using PHP. Websites may be briefly interrupted during those restarts. Older, unsupported distributions are outside the scope of this pass. Hosting panels, custom PHP installations and containers may also need separate work. We are still working on options for those servers. You can access the results of the work at: DetailsIf your VM serves PHP websites, please check for the security updates now. Install the patched packages and restart the processes running PHP. Please do not wait for our checking tool. The PHP project released fixes in 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Linux distributions may instead apply the fixes to an older PHP version while keeping its existing version number. Check the complete package version against your distribution's security advisory. A build date of 19th November 2026 or later is not proof that PHP is patched. Also, php -v reports the command-line PHP installation, which may differ from the PHP version used by your websites. If a patched package is unavailable, consider temporarily removing public access to affected PHP applications. A WordPress maintenance plugin or login page is insufficient: some attack paths run before the application's own code. Updating your server yourselfThese instructions are a starting point for servers using maintained package repositories. Servers with old operating systems, hosting panels, custom PHP builds or containers may need a different approach. Before updating, check that you have a current backup and access to your VM's console. Package updates and restarts can briefly interrupt websites and other services. Run the commands over SSH. If you are already logged in as root, omit sudo. 1. Identify your operating system and PHP packagesThese commands display operating-system information and the command-line PHP version: cat /etc/*release /etc/debian_version 2>/dev/null php -v On Debian or Ubuntu, list matching packages: dpkg-query -W -f='${Package} ${Version}\n' 'php*' 'libapache2-mod-php*'
On AlmaLinux, Rocky Linux, RHEL or CentOS: rpm -qa '*php*' If php -v reports "command not found", that does not establish that your websites do not use PHP. Hosting panels and custom installations may store their own PHP binaries elsewhere. 2. Install available updatesOn Debian or Ubuntu, refresh the package information and preview the updates: sudo apt-get update && sudo apt-get -s upgrade If refreshing the package information reports repository or signature errors, resolve those before continuing. Review the proposed changes, then install the updates: sudo apt-get upgrade Check whether any PHP packages were held back. If they were, the update may be incomplete. dist-upgrade can resolve additional dependencies, but it can also remove packages, so review its proposed changes before using it. On AlmaLinux, Rocky Linux or RHEL using DNF: sudo dnf --refresh upgrade On an installation using YUM: sudo yum clean all sudo yum update Review the package transaction before confirming it. These commands update packages from your configured repositories; they do not guarantee that those repositories contain the PHP2Shell fixes. "No updates available" is not confirmation that your server is safe. The fix may not yet be published for your distribution, your PHP stream may no longer receive updates, or PHP may come from another provider. AlmaLinux's response, for example, distinguishes supported and retired PHP streams: If you use cPanel, Plesk or another hosting panel, follow that vendor's PHP update procedure too. Updating the operating system's default PHP package may leave the versions serving your websites unchanged. 2a. MitigationsIf your application does not need the to track upload progress, set the following in php configuration and restart all php services... session.upload_progress.enabled = 0 This removes the easiest path to the flaw, not the flaw itself. You still need the upgrade. Also limit untrusted data your application stores in sessions. If session tracking is not needed for your site, disabling this may also help. The following are possibilities and should get targeted testing in your environment. # disable autmatic session tracking session.auto_start = 0 # disable url based session tracking session.use_trans_sid = 0 session.use_only_cookies = 1 3. Restart the processes using PHPPackage updates sometimes restart services automatically. Do not assume that happened successfully. Once patched packages are installed, rebooting the VM is a straightforward way to replace running processes: sudo reboot This interrupts all services on the VM. Confirm it returns and your websites work. Alternatively, restart the relevant services individually. On Debian/Ubuntu, for example, if you use PHP 8.3 FPM: sudo systemctl restart php8.3-fpm Replace 8.3 with your installed version. On RPM distributions, the service is commonly: sudo systemctl restart php-fpm These are examples: use your actual service names. Very old systems may use service or /etc/init.d/ instead of systemctl. If Apache runs PHP directly through mod_php, restart Apache instead: its service is commonly called apache2 on Debian/Ubuntu or httpd on RPM distributions. Restart every PHP version serving websites, plus long-running PHP workers. Restarting nginx alone does not restart PHP-FPM. Containers need their own updated images and replacement processes. 4. Check the resultRun the package-listing commands again and compare the installed revisions with the advisory for your package provider. Visit your websites and check that important functions still work. On Linux, this command can help identify PHP and web-server processes and their start times: ps -eo pid,lstart,args | grep -E '[p]hp-fpm|[a]pache2|[h]ttpd|[n]ginx' A recent process start time helps confirm a restart; it does not prove that the process loaded patched software. Older servers or unavailable updatesOlder servers may need migration to a maintained operating system, an extended-support service, or a carefully planned PHP upgrade. Some older Ubuntu releases have fixes through Ubuntu Pro/ESM, where that coverage is enabled. We are investigating options for older installations, including third-party repositories such as Sury. Please do not add repositories or switch PHP versions blindly: compatibility and available fixes depend on the operating-system release and application. If you cannot obtain a confirmed fix, remove public access to the affected PHP applications while arranging an update. If you would like RimuHosting to assist you migrating your server to a currently supported distro - which may require a reinstall and migration - please reach out to us. We can assist with these as time permits. The process is described at https://rimuhosting.com/knowledgebase/rimuhosting/migration | |
Log in to subscribe to changes to this notice.
Set your operation notice contact details for future notifications.