PHP2Shell Core RCE Advisory: Dissecting CVE-2026-109618 & CVE-2026-109619
The PHP Group and the Australian Cyber Security Centre (ACSC) have issued urgent warnings regarding two critical Remote Code Execution vulnerabilities in the core PHP interpreter: CVE-2026-109618 and CVE-2026-109619, collectively designated as PHP2Shell.
Carrying a CVSS 4.0 rating of 9.2 (Critical) and already added to CISA's Known Exploited Vulnerabilities (KEV) catalog, PHP2Shell allows unauthenticated remote attackers to execute arbitrary system commands on target web servers without valid credentials, application-level bugs, or prior authentication.
1. How the Vulnerabilities Work: OOM Corruption & Stale State
Unlike web application bugs (such as SQL injections or file upload bypasses in WordPress plugins), PHP2Shell exists directly inside the Zend engine's core memory allocator and request lifecycle handlers:
-
CVE-2026-109618 (Out-Of-Memory Corruption): When PHP encounters an Out-Of-Memory (OOM) error while parsing multipart payloads, it invokes
longjmp()to immediately abort execution. However, critical request data structures remain in a partially initialized state. During the subsequent cleanup pass, the engine branches or executes on uninitialized memory pointers, leading to arbitrary code execution. - CVE-2026-109619 (Stale Global State & UAF): During multipart request parsing, session upload progress trackers temporarily bind global pointers to request-allocated heap blocks. If interrupted, the global state fails to reset before the request heap is freed. When a subsequent request is routed to that same persistent worker, it references this stale memory (Use-After-Free), enabling remote memory leakage and execution sinks.
2. Affected Environments & Version Matrix
Every runtime architecture serving web requests is vulnerable: PHP-FPM, Apache mod_php, php-cgi, LiteSpeed, and FrankenPHP. While Apache mod_php presents the highest immediate risk (allowing execution before application code executes), PHP-FPM setups are actively exploited in the wild.
| PHP Series | Vulnerable Baseline | Patched Official Release |
|---|---|---|
| PHP 8.5 | Up to 8.5.11 | 8.5.12 or later |
| PHP 8.4 | Up to 8.4.26 | 8.4.27 or later |
| PHP 8.3 | Up to 8.3.35 | 8.3.36 or later |
| PHP 8.2 | Up to 8.2.34 | 8.2.35 or later |
| PHP 8.1 & Earlier (7.x / 5.x) | All versions (5.4 – 8.1) | No Official Upstream Patch (EOL) |
3. Real-World Damage & In-The-Wild Exploitation
Telemetric honeypots and threat intelligence desks observed weaponized probes within 4 hours of the vulnerability leak. Documented impact across compromised hosts includes:
Automated Webshell Drops
Adversaries deploy lightweight PHP web shells via encoded POST buffers, establishing root administrative footholds across WordPress and Laravel web roots.
Silent In-Memory Credential Dumps
The memory disclosure flaw extracts uninitialized heap data from prior transactions, exposing plain-text database credentials, session tokens, and TLS private keys without triggering error logs.
Container Escapes & Lateral Movement
Web processes compromised via PHP-FPM workers are leveraged to survey internal VPC networks, pivot to cloud databases, and probe Kubernetes cluster APIs.
Ransomware Staging
Automated payloads execute remote staging scripts to download and detonate encryptors across accessible local storage volumes.
4. Remediation & Mitigation Roadmap
The only definitive fix is updating the PHP engine to the patched point release and restarting all worker pools.
Step 1: Check Active Interpreter Version
php -v
Step 2: Emergency Workarounds (If Immediate Patching is Delayed)
If production freeze constraints prevent immediate package upgrades, apply the following configuration mitigations to reduce the attack surface:
; Disable vulnerable session upload progress tracking
session.upload_progress.enabled = 0
; Remove predictable single-request heap boundaries
memory_limit = -1
; On PHP 8.5 environments, disable backtraces
fatal_error_backtraces = 0
After editing php.ini, restart your web server and worker processes:
sudo systemctl restart php8.3-fpm && sudo systemctl reload nginx
Need Emergency Incident or Patch Support?
Flux IT’s Perth-based engineering team assists WA organizations with rapid vulnerability scanning, web application firewall (WAF) rule deployment, and PHP stack hardening.
Emergency PHP Triage
Ensure your web servers and hosting stacks are fully secured against PHP2Shell active exploitation.
Contact Flux IT