What are the PHP2Shell vulnerabilities?
Two newly disclosed vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619, put a widely deployed web runtime under scrutiny. In the worst case, an unauthenticated attacker could execute code in the affected PHP process. Exploitation is technically demanding and depends on the deployment, but the potential impact makes PHP2Shell PHP security updates a priority for teams that operate web applications. The flaws involve out-of-memory handling and stale request state, not necessarily a defect in an application’s own code. Reported outcomes include worker crashes and data exposure as well as possible code execution. Execution would inherit the PHP process’s permissions; it does not automatically grant root access. See the PHP project’s advisory for the technical details.
Why do the PHP2Shell vulnerabilities matter?
Security patches are now available in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35; Linux distributions may backport the fixes under different version numbers. Inventory every PHP runtime serving web requests, including separate application pools and hosting environments, then deploy the relevant security update or verified vendor backport. For older branches, consult your vendor’s advisory or plan an upgrade to a supported release. Confirm that the serving workers restarted onto the fixed build, and monitor memory-exhaustion errors, fatal errors and repeated crashes for anomalies; none alone proves exploitation. Temporary mitigations do not replace patching. The PHP version checker may assist an initial check, but its result should not replace server inventory; it was not independently accessible during our review. See also the technical analysis.