The short version
- The flaw. PHP2Shell covers CVE-2026-109618 and CVE-2026-109619, two critical PHP bugs that allow unauthenticated remote code execution. PHP shipped fixes on 21 October, a day early, after the CVE identifiers leaked.
- The attempts. Attackers have tried to install Potassium, a Mirai-derived botnet that launches DDoS floods. Sophos, which analysed one attempt, says it was stopped and has corrected an earlier report of successful exploitation.
- No confirmed breach. Hunt.io, Wordfence and SOCRadar report attempts and tooling but no confirmed compromise; SOCRadar found no screened site that met the exploit's preconditions.
- Patching lags. Qualys says only 199,000 PHP instances were patched within 12 hours of disclosure, and about 110 million instances, or 71%, run PHP 5.4 through 8.1, which are past end of life; most will never receive a vendor patch.
Timeline
| Date | Event |
|---|---|
| August | Wiz, OpenAI and Calif find the two PHP flaws, SecurityWeek reports. |
| 17 October | Amazon spots the first exploitation attempt, before any patch exists. |
| 21 October | PHP releases fixed versions a day earlier than planned, after the CVE identifiers leaked online. |
| 21 October | Several European government, school and hospital sites go offline as a precaution; the UK government says 32 of its services were unavailable and four partly unavailable. |
| 22 October | SOCRadar reports no shell access on any of the sites its discovered tooling screened. |
| 23 October | CISA has not added either CVE to its Known Exploited Vulnerabilities catalogue, as of that morning. |
The flaws and the fix
PHP2Shell is the name given to CVE-2026-109618 and CVE-2026-109619, two critical bugs in the PHP engine that allow unauthenticated remote code execution through crafted HTTP requests. Both score 9.2. Wiz, OpenAI and Calif found them in August, according to SecurityWeek, and PHP released fixes on 21 October, a day earlier than planned, after the CVE identifiers leaked.
Fixes exist in the current supported PHP branches; the PHP advisory lists the versions. Amazon spotted the first exploitation attempt on 17 October, before the patches existed, and activity rose once they shipped. On 21 October several European government, school and hospital sites went offline while systems were patched, and the UK government said 32 of its services were unavailable and four partly unavailable.
Botnet attempts and attacker tooling
Sophos analysed an attempt to install Potassium, which it believes is a variant of Mirai, a long-running family that conscripts Linux devices into DDoS floods. The attempt was stopped, so the malware never reached the target, and Sophos corrected an earlier update that had reported a successful exploitation. Arctic Wolf tied two Potassium binaries to servers hosting PHP2Shell payloads but said its data does not show the requests fetching or running the malware.
SOCRadar found PHP2Shell tooling on an attacker-controlled server whose working files were publicly browsable: an exploit chain for PHP 8.4.26 on Apache mod_php that the operator called one-click, plus scripts that fingerprinted about 20 websites in seven countries. None met the exploit's preconditions and no shell access was seen as of 22 October. Hunt.io, which examined the same server, counted 123 targeted servers and no successful exploitation.
Address space layout randomisation (ASLR), which scatters code and data in memory to frustrate exploits, had been a major obstacle. VulnCheck says its exploit for CVE-2026-109618 reaches code execution on x86-64 systems with ASLR enabled and PHP error display off, the recommended production setting, and offers it to Initial Access Intelligence customers. Sansec, which had predicted mass exploitation within 15 minutes of the patch, now says public exploits fail against default installations.
Exposure and the patching gap
Qualys, using anonymised data from 12,000 customers, says only 199,000 PHP instances were patched within 12 hours. It puts about 110 million instances, 71% of the total, on PHP 5.4 to 8.1, all past end of life and unlikely ever to receive a vendor fix; another 44 million run supported branches where fixes exist but had not been applied. Censys publishes a dashboard tracking vulnerable internet-facing PHP services.
As of the morning of 23 October, CISA had not added either CVE to its Known Exploited Vulnerabilities catalogue. Hunt.io, Wordfence and SOCRadar report attempts and preparation but no confirmed compromise, and no vendor has reported one.
What is not known yet
- Who is behind the exploitation attempts, and whether the Mirai operators and the tooling operator SOCRadar found are the same group.
- Whether any organisation has been compromised without public disclosure; no vendor has reported one.
- Whether VulnCheck's ASLR-bypassing exploit has been used in the wild or obtained by other attackers.
- Whether the wider screening run against 123 servers succeeded anywhere beyond the sites the two firms examined.
- Whether CISA will add the two CVEs to its Known Exploited Vulnerabilities catalogue.
What to do
If you run PHP
- Upgrade to a fixed release; 8.4.27 is the fix on the 8.4 branch and the PHP advisory lists the others.
- Move services off PHP 5.4 to 8.1, which are end of life and will not receive a vendor patch.
- Remove phpinfo pages and verbose error output, which the attacker screening scripts look for.
- Inventory internet-facing PHP services and check each one's version rather than relying on aggregate statistics.
If you defend a network
- Block the attack source, loader and command-and-control addresses published by Sophos and Hunt.io.
- Alert on DNS lookups for the domain Sophos published and on outbound traffic to its command-and-control address on TCP port 50792.
- Watch for flood traffic over ICMP, TCP, UDP and OpenVPN, the protocols Arctic Wolf says the Potassium build supports.
For everyone else
- Keep a current inventory of internet-facing software and versions so a critical disclosure can be triaged in hours.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.