- Published on
PHP2Shell: Remote Code Execution in PHP
- Authors

- Name
- Alex Lee
- Title
- CEO
- @alexjoelee
CVE-2026-109618 & CVE-2026-109619
On October 20th, information surfaced on social media regarding two upcoming Remote Code Execution vulnerabilities in PHP scheduled for official disclosure on October 22nd, 2026, at 18:00 CEST. The CVEs were assigned as CVE-2026-109618 and CVE-2026-109619, with CVSS scores not yet published. These vulnerabilities reportedly allow an attacker to execute arbitrary code on any server running PHP, potentially resulting in full server compromise. The unverified report claims both vulnerabilities affect every PHP version from PHP 5 onward, though no official vendor advisory has confirmed the scope, technical cause, or a fixed version at this time. Security teams should monitor official PHP security channels and prepare to update PHP installations promptly once a confirmed fix is released on October 21st, 2026 at 1400UTC.
Monitor for the patch release at php.net.
Update 10/21 0630UTC:
We have deployed additonal WAF rules to help detect and prevent these attacks. These rules detect some of the attack methods used to exploit these two vulnerabilities and block them. This is not a holistic a fix - the official recommendation here still is to take down your application until the patches and more information are released.
Update 10/21 1430UTC:
Patches have been released and at this time we are unable to deploy a meaningful defense rule against these attacks at the WAF level due to the nature of the attacks. Please see the official announcement and update all PHP installations as quickly as possible: php.net/archive/2026.php#2026-10-21-5
What We Can Do
These bugs aren't really in WAF territory. The memory corruption happens inside PHP's own runtime. zend_mm_alloc fails, the engine bails partway through setting up internal request structures, and then the cleanup handler walks through data that was never properly initialized. The stale-state one is even worse: a worker process holds onto freed memory from a prior request, and the next request through that worker grabs it before PHP's normal init sequence overwrites it. Our WAF does not see PHP's heap. Our WAF does not see what's left in a worker's zend_executor_globals from the last req. These aren't injection bugs where a WAF can pattern-match a payload. They're use-after-free and uninitialized-memory bugs. By the time the request hits the wire, the bits our WAF can inspect look normal. The problem is what PHP does with them internally.
We do have a few knobs we can turn to make things harder for an attacker. If you enable the OWASP Core Rule Set through the console — assuming you haven't already — it'll catch and block a lot of common command injection attempts at the edge. That doesn't fix the underlying bug, but it raises the bar for turning a successful memory corruption into actual command execution, because the attacker still needs to get their payload past our WAF to do anything useful with the corruption. It buys you some time. Beyond that, all platform users (including free) can contact support and we'll manually set a request body size cap on your origin traffic, which reduces the chance of someone triggering the OOM path in CVE-2026-109618 by limiting how much memory pressure a single request can create. We can also disable keep-alive from our edge to your origin — so each request hits a fresh connection, and workers don't sit around recycling stale state between requests for CVE-2026-109619. To be clear: none of this is a fix. The request size limit doesn't close the OOM bug, turning off keep-alive doesn't guarantee worker state gets cleaned, and CRS doesn't understand PHP memory corruption. These are stopgaps. The only thing that actually resolves the issue is applying the PHP patches - act accordingly!
Update 10/22 1230UTC:
We have not seen excessive exploitation attempts against sites on our network at this time. We are continuing to monitor for these attacks and will update the WAF rules to improve protections if possible. The only action that actually resolves these issues is applying the patches.