Critical PHP2Shell Vulnerabilities Prompt Urgent Patches
PHP has released patches for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, with CVSS 9.2 scores enabling unauthenticated remote code execution. The flaws affect nearly all PHP versions and 70% of websites globally, with active exploitation already observed.

PHP has released urgent patches for two critical-severity vulnerabilities, CVE-2026-109618 and CVE-2026 109619. These flaws, collectively named PHP2Shell, each carry a CVSS v4.0 score of 9.2 and enable unauthenticated remote code execution.
Widespread impact across PHP ecosystems
The vulnerabilities affect nearly all PHP releases back to version 5.4. They impact major web servers and frameworks including Apache with mod_php, PHP-FPM, php-cgi, FrankenPHP, and LiteSpeed. The flaws can read sensitive process memory containing passwords, authentication tokens, and API keys.
PHP powers approximately 70% of all websites globally. This includes major content management systems like WordPress, Drupal, and MediaWiki, which underpins Wikipedia. The risk is present regardless of the specific CMS in use.
Patches for both vulnerabilities are included in the following PHP versions:
| PHP Version | Patch Status |
|---|---|
| 8.5.12 | Patched |
| 8.4.27 | Patched |
| 8.3.36 | Patched |
| 8.2.35 | Patched |
Limited source backports are also available for PHP versions 7.4, 8.0, and 8.1. Organizations using these older releases should consult vendor advisories or upgrade to a supported version.
Active exploitation observed globally
Exploitation attempts targeting these vulnerabilities were detected in the wild both before and after the patch release. Multiple security firms, including WatchTowr, Hadrian, Patchstack, Cloudflare, and Vega, observed the activity. Cloudflare and Amazon Threat Intelligence also reported attempts.
Attackers are targeting PHP's session upload-progress path. A public proof-of-concept exploit has been released, increasing the risk of widespread attacks. Jake Knott of the responding teams noted the precarious situation. "Whilst nobody has been successful to date, we don’t expect that will last long," he said.
Patch availability and accelerated response
The coordinated disclosure timeline was accelerated due to a leak on October 20, 2024. The PHP Foundation pushed patches one day earlier than the scheduled October 22 date.
Several providers deployed protections ahead of the public announcement. Chainguard published fixed container images six hours before the coordinated release. Cloudflare deployed its protections nine hours prior.
Mitigation and detection guidance
The PHP Foundation states that updating is the only complete fix. For CVE-2026-109619, a temporary mitigation is to disable the affected feature by setting session.upload_progress.enabled=0 and restarting PHP workers. However, the foundation warns that such mitigations only reduce exposure to specific attack paths and do not make unpatched installations safe.
Security tools can help identify vulnerable systems. Qualys customers can use QID 45110 to detect PHP installations for review. The Qualys Deep Scan (QID 389102) helps find installations in custom directories and on secondary drives. Qualys TotalCloud and Container Security can identify vulnerable components in cloud AMIs, container images, and Kubernetes workloads. The InstaScan feature enables immediate exposure detection after distribution patches are released for Red Hat, Ubuntu, Debian, and Oracle Linux.
The vulnerabilities were discovered by researchers from Wiz, OpenAI, and Calif in August 2024. They involve out-of-memory corruption and a stale global state, leading to demonstrated remote code execution. An initial out-of-memory flaw was found in 2020 and rediscovered this year.
The PHP2Shell Emergency Briefing is scheduled for October 22 at 7am PT to provide further details on mitigation and threat context.





