Critical PHP vulnerabilities enable instant remote code execution
Two critical remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, were disclosed on October 20, 2026, and patched the next day.

Two critical remote code execution vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619, were publicly disclosed on October 20, 2026. Patches were released on October 21, 2026, at 14:00 UTC. Exploitation requires no authentication and allows arbitrary code execution as the web worker account, leading to high risks to confidentiality, integrity, and availability.
Security researchers demonstrated the exploit, informally named PHP2Shell, against major content management systems and frameworks. Successful attacks enable data theft, website defacement, and full system compromise. Apache deployments using the mod_php module are identified as the highest risk. Remediation requires runtime updates to PHP itself, not only updates to CMS platforms or plugins.
Multiple cybersecurity agencies and firms urged immediate action. The Australian Cyber Security Centre told organizations to identify PHP systems and prepare to patch. CERT-EU called for immediate patching even before the official fixes were released. Cloudflare deployed web application firewall rules for PHP2Shell on October 21, nine hours before the public disclosure.
Exploitation methods and detection
Exploitation could be rapid. Sansec experts warned that "widespread exploitation could begin within 15 minutes of the update’s release." The vulnerabilities involve complex memory handling errors. CVE-2026-109618 involves out-of-memory errors via longjmp() causing uninitialized memory. CVE-2026-109619 involves longjmp() fatal error handling leaving global memory pointing to freed regions. Both enable reliable remote code execution.
Security vendors have deployed extensive detection capabilities. TrendAI, Kaspersky, and Palo Alto Networks released rules across their platforms. Detection focuses on signs of web shell creation, suspicious process generation from web servers, and network traffic patterns associated with the exploits.
| Vendor | Product | Rule/Filter Name or ID | CVE Coverage |
|---|---|---|---|
| TrendAI | Endpoint Security IPS | Rule 1012754 | CVE-2026-109618, CVE-2026-109619 |
| TrendAI | TippingPoint | Filter 48534 | HTTP: PHP Core Upload Progress Use-After-Free Vulnerability |
| TrendAI | Network Detection and Response | Rule 6021 | CVE-2026-109618 |
| TrendAI | Network Detection and Response | Rule 6023 | CVE-2026-109619 |
| Kaspersky | Anti Targeted Attack (KATA) | Exploit.CVE-2026-109618.HTTP.C&C | CVE-2026-109618 |
| Kaspersky | Anti Targeted Attack (KATA) | Exploit.CVE-2026-109619.HTTP.C&C | CVE-2026-109619 |
Affected software and exploitation examples
The vulnerabilities impact a vast range of software built on PHP. Researchers demonstrated exploitation against WordPress, Drupal, Joomla, MediaWiki, phpBB, Magento, Laravel, Symfony, and WHMCS deployments. This broad scope shows the need for comprehensive vulnerability management across all web-facing assets.
For organizations managing containerized environments, remediation is complex. TrendAI Container Security includes falco rules for detecting PHP worker processes spawning shells and for identifying vulnerable container image tags. Endor Labs recommends upgrading affected PHP installations regardless of a container's current reachability status. Cortex Cloud's Supply Chain Attacks Portal can help identify affected assets to prevent vulnerable components from being reintroduced, and its CLI integrates into CI/CD pipelines to scan images and block vulnerable ones.
Palo Alto Networks Unit 42 rated both vulnerabilities a 9.2 on the CVSS 4.0 scale. The firm recommends reviewing the PHP Group’s security advisory and patching immediately. Its Cortex XDR customers can use XQL queries to search for signs of exploitation. The immediate remediation is to upgrade PHP to patched versions 8.2.35, 8.3.36, 8.4.27, or 8.5.12.





