Loading content...
Loading content...
Two critical PHP flaws allow unauthenticated code execution on servers running PHP 5.4 and later. Learn how exploitation exploded within hours, what is patched, and how to protect your sites.
PHP runs on a very large share of the web, so a flaw in the language engine itself is a very different thing from a bug in one plugin. PHP2Shell is the name given to two vulnerabilities, CVE-2026-109618 and CVE-2026-109619, disclosed on 21 October 2026. Both can let an attacker run code on a server without logging in, and they can also expose server memory such as passwords, tokens and API keys.
Reported severity is critical. Most sources cite a CVSS score of 9.2 for both flaws, while some posts cited 10/10, so treat the exact number as unsettled and the urgency as settled.
| Branch | Fixed version |
|---|---|
| PHP 8.5 | 8.5.12 |
| PHP 8.4 | 8.4.27 |
| PHP 8.3 | 8.3.36 |
| PHP 8.2 | 8.2.35 |
Cloudflare says releases as far back as PHP 5.4 are affected. Older, end-of-life branches will not receive an official fix, which makes them the highest-risk systems on the internet right now.
Cloudflare reported a steep curve of exploitation attempts around disclosure:
Governments reacted. The US NSA urged immediate patching or shutting systems down, the UK NCSC advised taking unpatched systems offline if necessary, and some public sector, school and hospital sites were pulled offline as a precaution.
Wiz reported that frontier AI models found the flaws, and OpenAI said one of them was discovered by its GPT-5.6 Sol model. The bugs reportedly sat in the codebase for more than a decade. That is the most important long-term point in this story: automated review can surface old bugs far faster than humans did, and attackers have access to similar tooling.