PHP2Shell: two 9.2 RCE flaws, exploit attempts before disclosure
CISA urges immediate patching of CVE-2026-109618 and CVE-2026-109619, two critical unauthenticated RCE bugs in PHP. Amazon saw an exploitation attempt four days before disclosure; both are now in CISA's KEV catalog.
PHP shipped four releases on October 21, 2026, closing two critical vulnerabilities known as “PHP2Shell”: CVE-2026-109618 and CVE-2026-109619, both rated 9.2 on CVSS (the Common Vulnerability Scoring System, a 0–10 severity scale). They allow unauthenticated remote code execution, meaning an attacker can run code on your server without logging in. On October 26, the US Cybersecurity and Infrastructure Security Agency (CISA) added both to its Known Exploited Vulnerabilities (KEV) catalog. US federal civilian agencies have until October 29 under the KEV directive; everyone else should act now.
What is affected
The flaws affect every PHP installation that serves web requests. CISA names Apache with mod_php, PHP-FPM, php-cgi, FrankenPHP and LiteSpeed. Because PHP is often bundled inside other software, a server can be exposed without anyone installing it directly.
The fix is in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and earlier are out of support and will not be patched; those systems stay vulnerable until upgraded or taken offline.
Why it matters in production
Unauthenticated RCE on an internet-facing service is close to the worst case: no credentials, no user interaction, a direct path from a web request to a shell. From there an attacker can read secrets, pivot internally, or drop a web shell.
The timeline is worse than the disclosure date suggests. Amazon Threat Intelligence reported an exploitation attempt against MadPot, its honeypot network, on October 17, four days before the flaws were public, from a commercial anonymization network. By release day it saw exploitation attempts from infrastructure suggesting multiple actors. Do not assume disclosure is the first compromise date; investigate from October 17.
What to do
- Inventory every system running PHP, including PHP embedded in other products. CISA notes prevalence is often not directly visible.
- Patch internet-facing systems first: upgrade to 8.5.12, 8.4.27, 8.3.36 or 8.2.35.
- If you cannot patch now, take the system offline or front it with a web application firewall. A WAF is partial mitigation; upgrading is the only complete fix.
- Hunt from October 17 onward: POST requests carrying
PHP_SESSION_UPLOAD_PROGRESSin form uploads, PHP workers spawning shells, and unexpected process or file changes. - Where you cannot patch right away, consider blocking multipart file uploads after testing the impact.
There is no configuration-only workaround for both bugs. The version bump is the fix; the log review can tell you whether you were already hit.
Sources
- CISA: Critical Vulnerabilities in PHP Require Immediate Patching
- AWS Security Blog: Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot
- The Hacker News: CISA confirms active exploitation of two PHP2Shell flaws
- CISA: Known Exploited Vulnerabilities catalog
- CrowdStrike: PHP2Shell, what to know
Related reading
3 postsDiscussion
Spotted an error? Send corrections to [email protected] .