← sources

PHP emergency release drops today. How are you finding the PHP you don't know you're running?

source: reddit (reddit:sysadmin)published 2026-10-21 04:53ingested 2026-10-22 02:41

retained text

Two critical PHP core RCEs (CVE-2026-109618 and CVE-2026-109619) leaked before disclosure, and the fixed releases are due today at 14:00 UTC. Reports say PHP 5 to 8 are affected and EOL branches may get no fix ([BleepingComputer](https://www.bleepingcomputer.com/news/security/php-warns-admins-of-two-critical-flaws-emergency-patches-coming-tomorrow/)). Huntress's write-up has a practical checklist: inventory every install, including php.exe and php-cgi.exe bundled inside vendor software and control panels like cPanel and Plesk, and isolate EOL PHP from the internet ([Huntress](https://www.huntress.com/blog/php2shell-leaked-critical-php-vulnerabilities)). The harder part is the external view: legacy sites and appliances on the internet that aren't in anyone's CMDB. [This overview of handling zero-day exposure](https://www.ctm360.com/blogs/what-is-a-zero-day-vulnerability) makes the same point: when patches are late or missing, asset visibility and temporary controls (restricting access, disabling the affected service) do most of the work.  
What's your fastest reliable way to enumerate PHP across servers, appliances and your external footprint? Package queries, EDR inventory, banner scans, something else?

document fetched 2026-10-22 00:40 · canonical https://reddit.com/r/sysadmin/comments/1xbe1iq/php_emergency_release_drops_today_how_are_you