PHP2Shell is actively being exploited. CISA added both CVE-2026-109618 and CVE-2026-109619 to its Known Exploited Vulnerabilities catalog on October 26, with federal agencies required to patch by today — October 29. Confirmed remote code execution was recorded in honeypots on October 24. The gap between patch release and first exploitation attempt was 19 minutes. If your PHP stack is not updated, you are inside an active attack window right now.
What PHP2Shell Actually Is
PHP2Shell is not a WordPress plugin bug. It is not a framework flaw. It is two use-after-free vulnerabilities in PHP’s core engine — CVE-2026-109618 and CVE-2026-109619, both rated CVSS 9.2. The code containing these flaws has been in PHP since version 5.4, roughly a decade of exposure hiding in plain sight.
The technical mechanics matter for understanding the severity. CVE-2026-109618 triggers when PHP runs out of memory during request setup, leaving partially constructed internal data that cleanup code incorrectly trusts. CVE-2026-109619 allows internal request state to survive after its backing memory is freed — a subsequent request to the same PHP worker can act on that leftover state before initialization resets it. Under Apache mod_php, a working exploit fires before your application code ever runs. Your WAF, your input validation, your authentication layer — none of it matters if you are unpatched.
Patch Versions: Update These Now
The PHP Project released fixed versions on October 21. These are not advisory updates.
- PHP 8.5 → 8.5.12
- PHP 8.4 → 8.4.27
- PHP 8.3 → 8.3.36
- PHP 8.2 → 8.2.35
PHP 8.1 and older received no official release. If you are running 8.1, use your Linux distribution’s package manager or contact your LTS vendor for a backport. PHP 7.3 and older have no fix path at all — upgrade the runtime.
After patching: restart Apache, PHP-FPM workers, and any long-running PHP processes. If you run containerized PHP, rebuild your images. Patching the binary without restarting leaves running workers still vulnerable. To confirm the patch is in place on Debian or Ubuntu:
apt changelog php8.3-cli | grep -E "CVE-2026-109618|CVE-2026-109619"
One post-patch note: the fixes add hard memory limits to PHP’s shutdown handlers. If your application runs with memory_limit=-1, review your memory settings after patching — you may see unexpected termination in memory-intensive processes.
The 19-Minute Window (There Wasn’t One)
Patches landed at 14:00 UTC on October 21. Exploitation attempts were logged at 14:19 UTC. That is not a window — it is a wall. Attackers were staged before the patches dropped.
This timeline reflects a new reality in offensive security. Researchers noted that demonstrating exploitability required “an exceptionally complex chain of steps.” In a prior era, that complexity would have bought defenders weeks. AI models compressed that development cycle from what would have taken a team months to roughly one week for a single researcher. The PHP Foundation acknowledged the structural failure: fixes had been theorized for years but stalled over compatibility concerns. AI did not create the vulnerability — but it eliminated the complexity moat that was partially protecting unpatched systems. The exploitation timeline documented by Bleeping Computer is as clear a case study as we have seen.
CISA KEV, DPRK, and Who Is Scanning Right Now
CISA added CVE-2026-109618 to its KEV catalog on October 26. Federal civilian agencies had three days to comply — deadline today. That is an unusually short window and signals how seriously the US government is treating active exploitation risk.
CYFIRMA has documented a suspected Lazarus Group (DPRK) campaign running a methodical, low-and-slow scan of 216 identified unpatched PHP hosts across the US, Japan, South Korea, Australia, Germany, and eight other countries. The operation routes through 21 compromised nodes and stays deliberately below detection thresholds. Target sectors include government agencies, financial institutions, logistics, and aviation infrastructure. Post-exploitation reconnaissance has used agentic AI to extract authentication database contents, pull Active Directory data via anonymous LDAP queries, and attempt privilege escalation. Help Net Security’s technical breakdown covers the vulnerability mechanics in detail.
This is not a script-kiddie campaign. The targeting is selective, the technique is deliberate, and the threat actor has a track record of converting infrastructure access into cryptocurrency theft and long-term espionage.
If You Cannot Patch Immediately
The official guidance is blunt: no configuration change fully mitigates either CVE. But if you cannot patch for hours, you can reduce the attack surface. For CVE-2026-109618: enforce request-size limits at your load balancer and set memory_limit=-1 via php_admin_value — counterintuitively, unlimited memory prevents the OOM trigger. For CVE-2026-109619: set session.upload_progress.enabled=0 in php.ini. Both measures are incomplete — treat them as delay tactics while you arrange the actual update.
After patching, or if you suspect compromise: monitor logs for multipart requests followed by HTTP 500 errors, check for new admin accounts or modified PHP files, and rotate database credentials and API keys. Memory disclosure means other requests’ secrets may have been read even without full code execution.
The Blast Radius
Around 5.1 million PHP hosts are exposed on the public internet. PHP powers an estimated 75% of websites using a server-side language — WordPress, Drupal, Joomla, Laravel, and thousands of custom backends. PHP2Shell does not require a vulnerable application. It requires a vulnerable runtime. That is almost every web application server on unpatched PHP. The watchTowr FAQ has step-by-step verification and remediation guidance.
Update your PHP runtime. Restart your workers. This is not a next-sprint fix.

