Emergency PHP security release fixes two unauthenticated RCE flaws (CVE-2026-109618, CVE-2026-109619)
On October 21, 2026, the PHP project shipped an emergency security release fixing two critical vulnerabilities in the PHP interpreter itself: CVE-2026-109618 (remote code execution via out-of-memory corruption) and CVE-2026-109619 (remote code execution via stale global state). Both are rated CVSS v4.0 9.2 and can let an unauthenticated attacker run code with the web worker’s privileges.
These flaws sit in the interpreter, not in WordPress or any plugin, so no plugin update and no application code change fixes them. Every PHP installation serving web requests is at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed. The PHP team considers mod_php the highest risk: it demonstrated an exploit where an unauthenticated request triggers the attack before any application code runs.
Details leaked on October 20, 2026, a day ahead of the coordinated disclosure, under the nickname “php2shell”, and the PHP project brought the release forward. By the morning of October 21, Cloudflare was reporting early attack traffic and had deployed emergency WAF rules, and Patchstack reported multiple active exploitation incidents from hosting partners. Wiz Research, which reported the flaws, says every PHP version back to 5.4 is affected by at least one of the two flaws and demonstrated unauthenticated remote code execution against current WordPress, Drupal, and Joomla container images.
The fixed releases are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. PHP 8.1 and older branches receive no official fix, though the security team published minimal source backports for PHP 7.4, 8.0, and 8.1, and some Linux distributions and LTS vendors carry their own fixes.
What to do
- Update PHP to the fixed release for your branch (8.5.12, 8.4.27, 8.3.36, or 8.2.35), or your vendor’s patched package, then restart every PHP worker. A web-server reload alone can leave old workers alive.
- Inventory every PHP installation you run: servers, containers, staging sites, appliances, and third-party software that bundles PHP. Each one needs checking.
- On PHP 8.1 or older, contact your vendor for a backported fix or upgrade to a supported branch. Running an unsupported interpreter on the public internet after this release is a major risk.
- Treat configuration tweaks (memory_limit changes, disabling session upload progress) as stopgaps only. The PHP project says updating is the only complete fix, and there are no complete mitigations.
Interpreter-level flaws like this are exactly what ZeroBreach’s server-layer audits and recurring scans are built to catch: the risk lives on the server, where no plugin or theme update can reach it.
Update, October 22, 2026
Exploitation of the PHP2Shell flaws has been confirmed at scale. Amazon Threat Intelligence logged an exploitation attempt on its MadPot honeypot on October 17, 2026, four days before the release, and watchTowr reports observing in-the-wild exploitation, with a variety of proof-of-concept requests hitting its sensors. Cloudflare reports millions of exploitation attempts and has pushed WAF rules for known vectors. No authority has published a count of successfully compromised systems.
The FBI Cyber Division warned organisations to patch immediately or take systems offline until they can, and to monitor web servers for suspicious activity, such as PHP processes unexpectedly launching command shells or downloading files. Several government services, including Dutch government services and the Dutch parliament’s website, temporarily went offline as a precaution. The campaign is active and broad; servers that were unpatched between October 17 and October 21 should be checked for compromise before being treated as clean.
Update, October 23, 2026
Attack traffic kept growing after the October 21 release. Cloudflare reported millions of exploitation attempts on October 22, 2026, and security vendors described the scanning as broad and indiscriminate.
Several organisations took sites offline as a precaution while they patched. The Netherlands took its DigiD and MijnOverheid services and a parliamentary site offline, several Australian government sites were disrupted, and the UK National Cyber Security Centre issued an alert urging organisations to update immediately.
Patching closes the door but does not say whether anyone entered. If a server ran an affected PHP version and was reachable from the internet after October 17, 2026, when Amazon logged the first exploitation attempt, it should be investigated for signs of compromise.
Update, October 25, 2026
Amazon Threat Intelligence said in a report published October 24, 2026, that the PHP2Shell flaws are being broadly exploited in the wild, while noting that it is unclear how many attacks have succeeded. Dataminr’s assessment differs in emphasis: observed activity since disclosure remains limited to scanning, fingerprinting, and non-working exploits, with no known compromises published as of October 22, 2026.
The two assessments agree on the action, not the outcome count: patch to a fixed PHP release, and investigate any server that was reachable from the internet while running an affected version. CISA updated its PHP2Shell alert on October 23, 2026, adding a Sigma detection rule for defenders hunting for exploitation signs.
Update, October 26, 2026
CISA added both PHP2Shell flaws to its Known Exploited Vulnerabilities catalog on October 26, 2026, with a federal remediation due date of October 29, 2026. The listing is an official confirmation that exploitation in the wild has been observed, and it moves this item from a patch promptly case to a patch first case for any operator that has not updated.
The action is unchanged: update PHP to 8.5.12, 8.4.27, 8.3.36, or 8.2.35, or a vendor patched package, and investigate any server that was reachable from the internet while running an affected version. Patching does not remove a backdoor that is in place.
Update, October 27, 2026
Attackers turned PHP2Shell probing into working shells on October 24, 2026. Researcher Adel Karimi reported 35 shells across three honeypots running PHP 8.4.26 under Apache mod_php with a single worker, from two IP addresses, using a four-stage request chain that exhausted memory, leaked memory contents, and executed a shell command, in traffic matching a public proof of concept. Karimi cautioned that the honeypot setup was deliberately favorable to the attacker, so the result does not measure exploit reliability on other worker counts, PHP builds, or applications. No second-stage payload download was observed in that honeypot activity.
The action is unchanged: update PHP to 8.5.12, 8.4.27, 8.3.36, or 8.2.35, or a vendor patched package, restart every PHP worker, and investigate any server that was reachable from the internet while running an affected version. CISA set a federal remediation due date of October 29, 2026 for both flaws, and patching does not remove a backdoor that is in place.
Update, October 28, 2026
The exploitation evidence for PHP2Shell became more precise on October 27, 2026, without changing the patch action. CISA added both flaws to its Known Exploited Vulnerabilities catalog on October 26, 2026, with a federal remediation due date of October 29, 2026, and that listing stands. Two vendors walked back specific successful exploitation claims in the same reporting: Sophos corrected an initial report, saying its telemetry showed scanning and a small number of failed attempts with no evidence of successful compromise, and Palo Alto Networks Unit 42 said it could not confirm PHP2Shell was the entry point in an attack against a European government agency. The scale of successful compromise remains unclear in public reporting, while honeypot evidence of working shells was already documented in the October 27, 2026 update.
The action is unchanged: update PHP to 8.5.12, 8.4.27, 8.3.36, or 8.2.35, or a vendor patched package, restart every PHP worker, and investigate any server that was reachable from the internet while running an affected version. Patching does not remove a backdoor that is in place.