Tip: get ready for tomorrow's PHP emergency fix tonight: find every PHP runtime, image and appliance, and pre-stage the rebuild
PHP's fix for two critical bugs lands Oct 21 at 14:00 UTC (details). Details have already leaked, so the gap between patch and exploit may be short. Tonight:
- Find it everywhere. On hosts:
php -vandphp -i | grep -i 'Server API', plusls /etc/php* /opt/*/php* 2>/dev/null; for packages,dpkg -l 'php*'orrpm -qa 'php*'. In containers, search Dockerfiles forFROM php:and scan running images with your SBOM tool (for examplesyft <image> | grep -i php). - Don't forget the hidden ones: WordPress, Drupal, Magento and Laravel hosts, vendor appliances with a PHP web UI, CI runners, and shared-hosting or managed-platform accounts where the provider patches for you (check their status page).
- Pre-stage the update. Know which repo you pull from (distro, Ondřej Surý PPA, Remi, official Docker images) and whether it usually ships same day. Distro backports can lag the upstream release.
- Shrink exposure until then: put internet-facing PHP apps behind your WAF, take test, staging and abandoned PHP sites offline, and isolate PHP 5/7 hosts that won't get fixes.
- After patching, restart PHP-FPM or Apache so the new binary is actually loaded, and confirm with
php -vand a phpinfo check on the live pool.
Sources: php.net: Upcoming Critical PHP Security Release · watchTowr on X (Oct 20)