Start with the production runtime
The PHP project advisory names installations serving web requests, including PHP-FPM (a separate PHP process manager), Apache with mod_php (PHP running as part of the Apache web server), php-cgi (PHP called as a separate program), FrankenPHP and LiteSpeed. It identifies mod_php as the highest-risk mode in its demonstrated exploit. First identify which setup actually handles production traffic; do not infer this from a content management system dashboard or a developer workstation. PHP project security advisory: critical remote code execution vulnerabilities, 21 October 2026
Ask the right owner
The runtime may be controlled by a hosting provider, managed service provider, platform team, software vendor or internal developer. Ask the person responsible for production operations to answer these questions and retain the response with the asset record.
- Which production hosts, containers or managed services run PHP for this application?
- Which PHP runtime mode (the setup that passes web requests to PHP) serves the application on each one?
- What exact upstream version or vendor package release is installed?
- Has the vendor included the applicable fix, including a possible patch applied to an older package version? What evidence confirms it?
- Were all serving instances and long-running workers updated or restarted as required by the vendor?
Compare the package, not just the version string
The PHP project lists fixed upstream releases for PHP 8.5, 8.4, 8.3 and 8.2. Linux distributions and long-term-support vendors may ship patches on their own package versioning schemes. A package can therefore include a security fix without matching the upstream version string. Conversely, a front-end version report may not represent every node in a production pool. Check the vendor advisory and package changelog for the system you actually run. PHP project security advisory: critical remote code execution vulnerabilities, 21 October 2026
PHP 8.1 and older no longer receive updates from the PHP project, although some distributions or vendors may provide security fixes for their own packages. Confirm your provider’s support commitment and patch status; if there is no maintained package, plan a supported-version upgrade. PHP 2026 news archive: supported branches and security releases
Check every relevant environment
Build a short inventory of public production endpoints and the runtime behind each. Include secondary regions, failover nodes, containers, scheduled workers and older hosts that may still serve traffic. Check staging separately: it helps test changes but does not prove production is updated. Record the owner, package evidence and verification date for each environment.
What this check can and cannot tell you
An inventory and vendor confirmation can establish whether the expected package is present. They may not establish whether a specific vulnerable condition was reachable, whether every deployment path was covered or whether there was prior malicious activity. Treat exposure validation and compromise investigation as different work. If unexplained activity is present, use your incident process and preserve relevant records.
A practical next-step record
Capture the application and environment, runtime mode, package/vendor version, advisory consulted, fix evidence, nodes verified, responsible owner, date and remaining uncertainty. If you cannot obtain reliable answers from the provider, a scoped application security assessment can help validate the technical evidence.

