Google cloud updated its PHP2Shell security advisory on October 23 with additional guidance from Mandiant Consulting.
CVE-2026-109618 and CVE-2026-109619
Both are critical remote-code-execution vulnerabilities affecting PHP.
The updated guidance emphasizes that installing patched packages does not necessarily mean the running web application is protected.
Older PHP processes may remain active in memory until the relevant web-serving services are restarted.
Researchers also recommend preserving volatile forensic evidence before restarting servers suspected of compromise.
Google additionally announced new detection capabilities for identifying potentially vulnerable systems and suspicious activity.
Why onion-service administrators should care
An onion service running PHP can remain vulnerable even when Tor successfully hides its hosting infrastructure.
Administrators should verify that the web server actually uses a patched PHP runtime.
For supported upstream branches, the initial fixed releases are PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. Distribution-specific security backports may use different version numbers.
Review logs dating back to October 17, when Amazon Threat Intelligence observed early exploitation attempts.
Confirmed exploitation attempts do not automatically establish successful server compromise.
Recommended action: Patch, restart the appropriate services, verify the running version, and investigate suspicious activity. Preserve evidence first if compromise is suspected.