November 22, 2026

Ubuntu Issues Urgent Security Patches for Critical ‘php2shell’ Flaws and Compromised eMudhra Certificates

Addressing the Flaws and Securing Systems

Canonical has confirmed that the php2shell vulnerability affects all Ubuntu versions operating with PHP version 5 or newer. However, official distribution patches are restricted to Ubuntu releases that currently remain within Canonical’s active maintenance and Long Term Support (LTS) lifecycle.

Fixes have been backported and distributed for supported releases ranging from Ubuntu 14.04 LTS all the way through the newest long-term support release, Ubuntu 26.04 LTS, as well as the standard interim release, Ubuntu 26.10. Systems operating on unsupported or end-of-life releases will not receive the official updates, leaving them permanently exposed unless upgraded to a supported operating system base.

For desktop systems, applying the necessary protections requires minimal administrative effort. Users can open the built-in Software Updater graphical utility, scan for pending package updates, and apply all pending software upgrades to receive both the patched packages and the updated certificate store.

For server environments, cloud deployments, and remote virtual machines where PHP services are active, administrators are urged to take prompt manual action to verify their patch status or contact their managed hosting providers to ensure protective measures have been implemented.

In standard administrative scenarios, applying all pending updates across the distribution can be completed through the advanced package tool by executing:

sudo apt update && sudo apt upgrade

Enterprise administrators often manage complex, tightly coupled application environments where performing an indiscriminate, system-wide software upgrade is not feasible due to stability and dependency concerns. In these circumstances, the targeted PHP and certificate packages can be updated individually without altering the wider system packages.

Canonical has highlighted an essential operational caveat for server environments: updating the underlying disk binaries alone does not instantly neutralize memory-resident vulnerabilities. Any application, daemon, web service, or background task utilizing the PHP interpreter must be restarted manually after the update process finishes. If an administrator cannot easily identify or isolate every running process that interacts with the PHP engine, performing a full system reboot is recommended to ensure all active services reload the secured libraries.