What is CVE-2026-109618 and CVE-2026-109619?
- Oct 22, 2026
- Michelangelo Sidagni
CVE-2026-109618 and CVE-2026-109619, collectively known as PHP2Shell, are critical remote code execution (RCE) vulnerabilities in the core PHP engine. Disclosed in October 2026, these engine-level memory safety flaws allow unauthenticated remote attackers to execute arbitrary code or access process memory on vulnerable PHP application servers.
CVE-2026-109618 (RCE via OOM Corruption):
An attacker triggers an Out-Of-Memory (OOM) fatal error during request parsing. PHP’s exception handling via longjmp() interrupts execution, leaving internal request data only partially initialized. When PHP executes request shutdown, it incorrectly treats uninitialized memory structures as valid, resulting in engine-level heap corruption and remote code execution.
CVE-2026-109619 (RCE via Stale Global State):
A fatal error or out-of-memory condition causes PHP to abort a request without properly clearing persistent worker state. Internal pointers retain references to request-owned memory regions after they are freed. Subsequent requests handled by the same persistent worker process operate on these dangling pointers, leading to a Use-After-Free (UAF) condition, memory leakage, and arbitrary code execution.
Impact:
Successful exploitation allows unauthenticated remote attackers to achieve remote code execution as the web worker account (e.g., www-data) or leak sensitive process memory.
Mitigation:
The PHP development team released official security updates addressing both vulnerabilities on October 21, 2026. System administrators must upgrade PHP to one of the patched versions: 8.2.35, 8.3.36, 8.4.27, or 8.5.12.
Disabling unused features such as session.upload_progress.enabled=0 in php.ini serves as an additional preventative hardening measure.
According to vendor advisories and threat ratings, CVE-2026-109618 and CVE-2026-109619 carry a CVSS v4.0 Base Score of 9.2 (CRITICAL) and fall under CWE-416 (Use After Free) and CWE-457 (Use of Uninitialized Variable).
PHP 5.x (All versions) PHP 7.x (All versions) PHP 8.0 (All versions) PHP 8.1 (All versions – End of Life, unpatched) PHP 8.2 (Versions prior to 8.2.35) PHP 8.3 (Versions prior to 8.3.36) PHP 8.4 (Versions prior to 8.4.27) PHP 8.5 (Versions prior to 8.5.12)
These vulnerabilities are exploitable remotely over HTTP/HTTPS by sending specially crafted, oversized, or multipart payload requests designed to exhaust worker memory allocation or trigger fatal errors during processing. Because execution happens below the application layer in the PHP engine itself, traditional Web Application Firewalls (WAFs) and application-level logs may fail to show malicious activity.
Apply official PHP engine updates immediately. End-of-life branches (such as PHP 5.x, 7.x, 8.0, and 8.1) will not receive official vendor patches and must be upgraded to a supported PHP release stream. Please reference official vendor advisories and OS distributor security channels for version-specific updates.
Deployments running Apache mod_php are at immediate risk, whereas PHP-FPM environments feature process recycling that mitigates certain early initialization vectors. However, updating the underlying PHP engine remains the only complete fix.