We flagged the PHP2Shell patches yesterday and told you to confirm every PHP server was on the new version. Amazon now says that was not the whole job. Its honeypots caught an exploit attempt on October 17, four days before PHP shipped the fix.
A patched server can still have been hit while it waited. Amazon’s advice is to start any investigation on October 17, not on the October 21 release date.
Amazon caught a PHP2Shell exploit attempt four days before the patch. If your server was online, check its logs back to October 17.
The 5-Minute Cyber BriefDon’t Miss the Policy Changes That Affect Security Decisions
Get the key CISA actions, new regulations, guidance, and risk shifts in a quick daily brief.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Amazon saw PHP2Shell attacks four days before the patch
Amazon Threat Intelligence says its MadPot honeypots recorded a PHP2Shell attempt on October 17 from an IP address tied to a commercial anonymization network. It is not clear how the attacker had exploit details while the bugs were under embargo.
Between 02:00 and 08:00 UTC on October 21, before the 14:00 UTC release, Amazon saw more attempts from other anonymized infrastructure with different payloads, which it reads as several actors. AWS CISO CJ Moses says PHP2Shell is now seeing broad exploitation attempts in the wild. Amazon says it is unclear whether any of the early attempts would have worked on real systems.
PHP servers that were online before they were patched
BleepingComputer, citing VirusTotal, says more than 5.1 million PHP hosts are exposed online. The fix only arrived on October 21, so any server that was online on October 17 had at least four days in which an attacker could have planted a web shell. Updating PHP does not remove one.
CISA’s alert asks defenders to watch for PHP worker processes launching shells or downloading tools. That check now needs to cover the days before the patch too.
Search web and process logs back to October 17
- Pull web server logs from October 17 onward for internet-facing PHP sites and search for POST requests carrying
PHP_SESSION_UPLOAD_PROGRESSin form uploads. - Search those logs, firewall logs and WAF logs for the six IP addresses Amazon published, and investigate hits rather than just blocking them (some are shared VPN exits).
- Look for new or changed PHP files in web roots since October 17 and for PHP-FPM or Apache processes that spawned shells, curl or wget.
- If a server still is not on 8.5.12, 8.4.27, 8.3.36 or 8.2.35, Amazon suggests blocking multipart uploads until it is, after checking what that breaks.
Forward this
For whoever runs our websites: Amazon says attackers were trying the PHP2Shell flaw four days before the patch came out. Being patched now is not enough; can we check our PHP servers’ logs and files back to October 17 for signs someone got in?
Details
- CVE-2026-109618 (RCE via out-of-memory corruption) and CVE-2026-109619 (RCE via stale global state), CVSS v4.0 9.2 each. Fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
- Amazon IOCs: 103.216.220.92 (October 17); 31.223.184.166, 37.19.200.5, 134.209.159.64, 103.114.163.188 and 95.217.98.37 (October 21).
- KEV: not in CISA’s catalog as of version 2026.10.21.
Hunt / verify
- Compare file modification times in web roots and upload folders with your deploy history since October 17.
- Review outbound connections from web servers since October 17 for downloads from unfamiliar hosts.
- Recheck the running version with
php -vandphp-fpm -vafter any restart.
Source: Amazon Threat Intelligence, October 21, 2026; CISA alert
Sources
- AWS Security Blog: Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot
- BleepingComputer: Amazon says PHP2Shell exploitation began 4 days before patches
- CISA: Critical Vulnerabilities in PHP Require Immediate Patching
- CVE.org: CVE-2026-109618
- CVE.org: CVE-2026-109619
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.