PHP2Shell refers to two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, both rated CVSS 9.2, in core PHP , the scripting language that runs 70% of all websites. They allow an unauthenticated attacker to run code on web servers and read sensitive memory including passwords, tokens, and API keys. The patch was released October 21, 2026. Amazon’s threat intelligence team detected active exploitation on October 17 , four days before the fix was available.
What PHP2Shell Actually Is
PHP2Shell was discovered by Wiz Research, a team of security researchers who used AI models , specifically Wiz Atlas, Gemini 4 Argon, and GPT-5.6 Sol to find vulnerabilities that had been sitting in PHP’s codebase for more than a decade without being discovered or exploited.
Both CVEs are memory-safety bugs. They stem from how PHP handles fatal errors, particularly out-of-memory errors, when processing web requests. In short, PHP can leave corrupted state behind after a request fails unexpectedly. A later request handled by the same worker can stumble into that stale state and an attacker who knows how to trigger the right sequence can use it to run code on the server or read memory that belongs to other requests.
The memory disclosure piece means an attacker can pull out passwords, session tokens, API keys, and certificates , information flowing through the server for completely unrelated requests. The remote code execution piece means they can run commands directly on the server, without needing any login credentials. Both attacks work before authentication.
Wiz demonstrated successful pre-authentication RCE against WordPress, Drupal, and Joomla , using their latest official container images. These are three of the most widely deployed content management systems on the internet. The vulnerabilities aren’t flaws in those applications. They’re in PHP itself, which means any PHP application is potentially affected.
70% of the Web Is a Lot
PHP powers WordPress, Drupal, Joomla, Magento, and MediaWiki , the software that runs Wikipedia. In Australia, it’s also the foundation of GovCMS, the platform behind a large number of federal government websites. W3Techs data puts PHP at 69.3% of all websites with a known server-side language.
Every PHP version released in the last decade is affected by at least one of these vulnerabilities. That includes versions 8.2, 8.3, 8.4, and 8.5, which have patched releases available. But it also includes 7.4 through 8.1, where the PHP security team published source backports only , helpful if you compile PHP yourself, less so otherwise. And it includes anything older than 7.4, which gets nothing at all from the project.
The Australian Cyber Security Centre issued an alert on October 21. Its first instruction was to “identify PHP within their environments.” Not patch it. Find it first. That order is deliberate. Under Essential Eight requirements, a critical vulnerability in an internet-facing service should be patched within 48 hours. That clock assumes you already have a complete list of where PHP is running. Most organisations don’t.
Why the 48-Hour Window Is Nearly Impossible
This is the inconvenient reality behind the patch timeline. PHP doesn’t just exist on servers that security teams commissioned and manage. It’s on microsites built for a 2019 campaign that nobody decommissioned. It’s on WordPress installs set up by marketing. It’s inside vendor-managed customer portals. It’s in container images pulled from public registries and never rebuilt.
When a CISO asks where the organisation is running PHP, the realistic answer involves several teams and several days. By the time a comprehensive list exists, the 48-hour window has closed for most of it.
Then there’s a second problem even once you’ve found it. Installing an updated PHP package doesn’t stop a running process. PHP-FPM or Apache has to be restarted for the new code to take effect. A remediation report that checks package versions without verifying running processes will overcount what’s actually been fixed.
Amazon’s threat intelligence team detected exploitation attempts against its honeypot network on October 17 , four days before the patch landed. CISA added both CVEs to its Known Exploited Vulnerabilities catalogue on October 26. Attackers had a working exploit and were using it before most defenders had even started their asset inventory.
This pattern of dark web early warning preceding public disclosure has become a consistent theme through 2026 , the information that matters most for defenders frequently exists in underground channels before it reaches official advisories.
AI Found It, AI Can Exploit It
The Wiz Research team is explicit about what changed here. The vulnerable code had existed in PHP for more than a decade. Human researchers hadn’t found a practical path to exploitation. With AI, that changed.
Turning these memory bugs into working exploits required chaining multiple flaws and accounting for how PHP allocates memory across requests. It’s the kind of multi-step, iterative analysis that is difficult for a single researcher to sustain across different PHP versions and configurations. With Gemini 4 Argon and GPT-5.6 Sol helping to adapt and debug the exploit, what would have taken a world-class team months took one researcher a week.
Raluca Ada Popa, Head of Gemini Security at Google DeepMind, noted: for over a decade these critical vulnerabilities remained unaddressed because vulnerability discovery and exploitation were incredibly complex. AI changed that.
The implication cuts both ways. AI helped defenders find and patch these vulnerabilities through coordinated disclosure. The same capabilities make it easier for attackers to develop similar exploits going forward. As we’ve covered when looking at how AI is lowering barriers across the whole criminal ecosystem, the reduction in barrier to entry applies symmetrically. What the Wiz team could build in a week, a well-resourced threat actor could also build in a week.
What You Should Actually Do
If you run any web infrastructure, the action list is specific.
Find where PHP is running. Not just the servers you manage directly. Include vendor-managed portals, legacy microsites, container images, and anything managed by other departments. This list is the gating step for everything else.
Check versions. PHP 8.2 through 8.5 have patched releases from October 21. Apply them. For anything older, assess whether migration or isolation is feasible.
Restart after patching. Updating the PHP package without restarting PHP-FPM or Apache leaves the old code running in memory. The update isn’t complete until the service restarts.
Check whether exploitation may have already occurred. Amazon detected honeypot activity on October 17. If you have internet-facing PHP systems, check logs from that period for unusual multipart requests, repeated HTTP 500 errors, unexpectedly large PHPSESSID response cookies, or unusual PHP worker restarts. These are the signals Wiz identified as potential indicators.
The CISA Known Exploited Vulnerabilities catalogue lists both CVEs and applies to federal agencies under CISA’s binding operational directive, but the guidance is worth following for any organisation with internet-facing PHP.
Whether your data has already been exposed in the exploitation window between October 17 and whenever your patch landed is a question worth assessing. Our guide on what to do when data may have been exposed covers the response steps that apply if sensitive server memory was accessed.
Frequently Asked Questions
What is PHP2Shell?
PHP2Shell is the name for two critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619, both CVSS 9.2) that allow unauthenticated attackers to execute code on web servers and read sensitive server memory. Discovered by Wiz Research using AI, they affect 70% of all websites.
What applications are affected?
Any application running on a vulnerable PHP version — including WordPress, Drupal, Joomla, Magento, MediaWiki, and GovCMS. The vulnerabilities are in PHP’s core engine, not in the applications themselves.
When was it patched?
October 21, 2026. PHP released fixed versions for supported 8.x branches on that date.
Were attacks happening before the patch?
Yes. Amazon’s threat intelligence team detected exploitation attempts against its honeypot on October 17, four days before the patch was public.
Why did dark web forums go offline?
Because they run PHP , and attackers with the exploit could use it to access member data, private messages, and stolen credentials on forum servers. BreachForums messaged members about security. DarkForums shut down completely.
What should I do now?
Find all PHP installations across your environment, patch to supported 8.x versions, restart PHP-FPM or Apache after patching, and review logs from October 17 onward for signs of exploitation.