PHP2Shell is the name given to two memory-safety flaws in PHP, tracked as CVE-2026-109618 and CVE-2026-109619 and rated 9.2 under CVSS v4.0. Both allow an unauthenticated attacker to run code on a server simply by sending it a crafted web request. They affect PHP 5.4 through 8.5, which covers almost every PHP installation in use today, including WordPress, Joomla and many web-based management portals on network appliances.
What has happened so far
- 17 October: Amazon’s threat intelligence team saw a first exploitation attempt, four days before public disclosure.
- 21 October: PHP released fixed versions. Within two hours, Cloudflare recorded hundreds of thousands of exploit attempts, rising to millions by the next morning, and honeypots run by watchTowr saw live exploitation. Some government websites in Europe and Canada were taken offline as a precaution.
- 23 to 25 October: Researchers at Dream reported that a suspected China-nexus actor had chained PHP2Shell with a Linux kernel flaw (CVE-2026-46300). The attacker gained root on 25 servers, mostly internet-facing firewalls, in the US, Japan, Taiwan and South Korea, including three systems in a US government-affiliated network.
- 30 October onwards: Check Point Research reported that attackers used PHP2Shell, together with a separate privilege escalation flaw (CVE-2026-123039), to compromise Check Point Mobile Access and Security Gateways. In a first wave against Israeli organisations, the attackers moved on to VMware ESXi hosts and ran a wiper.
Mass scanning is also being used to spread a Mirai-based botnet. Reliable exploitation of real targets is harder than early reports suggested, but it is clearly achievable by skilled attackers, and the firewall campaigns show that it is already happening.
What to do now
- Update PHP to 8.2.35, 8.3.36, 8.4.27 or 8.5.12, or apply your hosting provider’s or Linux distribution’s backport. PHP 7.3 and older will not be fixed and should be retired.
- Check the version actually serving web requests, not just the command-line PHP, and restart all PHP workers after updating.
- Do not rely on configuration workarounds. The PHP maintainers say they are incomplete. If a system cannot be patched today, restrict internet access to it.
- Patch your network appliances. Many firewall, VPN and management portals run PHP. Check Point customers should follow advisory sk1000362; for other vendors, check their PHP2Shell advisories.
- Hunt for signs of compromise from 17 October onwards: unexpected files in web or template folders, new scheduled jobs or accounts, crashed PHP or web server workers, and unusual outbound connections from servers or appliances.
Sources: watchTowr: PHP2Shell intelligence; Check Point Research: PHP2Shell exploitation on Check Point gateways; The Hacker News: PHP2Shell attack roots 25 servers.