Supported branches received another security update

On 19 November, PHP released security updates for the 8.2, 8.3, 8.4 and 8.5 branches: 8.2.36, 8.3.37, 8.4.28 and 8.5.13. The change log describes fixes across core and components such as CGI and FPM. The critical cases PHP flagged ahead of release require particular configurations or uncommon setups; they should not be described as universal, unauthenticated code execution.

This is a new release cycle, separate from October's PHP2Shell vulnerabilities. A team that completed the earlier emergency patch still has to assess the November fixes. PHP 8.6.0 was also released on 19 November, but moving a production application to a new major branch is a separate compatibility decision.

Do not close the ticket at package installation

A system can have a fixed PHP package on disk while an older FPM worker, container image or bundled runtime continues to serve requests. Check the live process and restart it as required.

Find what is actually executing requests

  1. 1

    Inventory runtimes. List PHP versions across hosts, containers and application images. Note the server integration in use, such as PHP-FPM, CGI or an embedded runtime.

  2. 2

    Patch the applicable branch. Use the current security release or a vendor-maintained backport for the installed branch. Review the PHP change log for component-specific exposure and test application compatibility.

  3. 3

    Verify after restart. Confirm the running PHP process and image digest changed, then check that the application still serves requests normally. Keep earlier PHP2Shell look-back work separate from this patch validation.

The runtime boundary is the evidence

Version scanners often read a package database or a repository lockfile. Neither proves what code handled the last web request. For this release, keep a short record of the running binary, service restart and image rollout. It makes the patch status defensible when several PHP copies live on the same host.