Lead · Vulnerabilities
PHP2Shell was in the wild four days before the fix, and most of what hit the sensors afterwards does not work
Two critical PHP remote code execution flaws were patched on Wednesday afternoon; Amazon's honeypots had been watching people try them since Saturday.
The PHP security team shipped emergency fixes at 14:00 UTC on 21 October for CVE-2026-109618 and CVE-2026-109619, known together as PHP2Shell, in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and said plainly that only updating fully protects a server. Amazon Threat Intelligence then reported that its MadPot telemetry caught exploitation attempts on 17 October, four days before anyone outside the room had a patch to install. Brian Krebs put the exposure at nearly 70 percent of websites needing to update their core software, and by Wednesday afternoon hundreds of sites were offline as the maintainers' warning worked its way through the world's hosting panels.
The industry could not agree on how bad it was while it was happening. SANS raised its infocon to yellow citing a CVSS of 9.4 and early proof-of-concept exploits circulating before the patch; other coverage the same morning carried 9.2. The PHP Foundation's own account is the uncomfortable part: a third-party review by AI companies in August is what sharpened attention, and one of the two bugs dates to 2024, which means the flaw was ontologically present in your estate for two years and merely lacked a name, a logo and a CVSS argument. The single setting being passed around as a workaround is, according to the firm that suggested it, not enough on its own.
Then the noise arrived. A researcher watching a honeypot network reported being blasted with php2shell exploits that not only do not work but are not within ten thousand miles of how the bug actually works, because people are feeding loose details into language models, the models fixate on the PHP_SESSION_UPLOAD_PROGRESS string, and out comes confident session-poisoning code aimed at the wrong thing entirely. Treat 'mass exploitation' as an unverified word until your own telemetry says it. Meanwhile the quiet, real work has started: Okta has already patched four Access Gateway flaws including PHP2Shell, fixed in 2026.44.0, and vendors across the board are checking whether they shipped PHP inside something you bought as an appliance.
Why it mattersPatch PHP everywhere, including the places where PHP is somebody else's product with a vendor sticker on it, and search logs back to 17 October rather than to Wednesday.
- 1RSSPHP ships emergency patches for critical PHP2Shell…
- 2Security newsPHP2Shell Patches Land as First Exploitation Attemp…
- 3Security newsCritical PHP Vulnerability (CVE-2026-109618, CVE-20…
- 4Security newsPHP2Shell: Two Unpatched Critical PHP RCE Flaws (CV…
- 5Security newsPHP Issues Emergency Patches for Two Critical PHP2S…
- 6RSSAmazon says PHP2Shell exploitation began 4 days bef…