What changed in the PHP releases

The PHP project released security updates for supported PHP branches on 19 November 2026. The project says these releases fix critical security issues. PHP administrators should check the official release notes and their operating system or hosting provider for the correct package.

A version number alone does not show whether a system has the vendor patch. Some Linux vendors backport fixes without changing the upstream version in the same way. Check the package advisory for your platform and record the package that was installed.

Find all PHP runtimes

Check PHP-FPM pools, Apache modules, command-line jobs, queue workers, containers and application platforms. A server can run more than one PHP version. A website can also use a runtime supplied by its hosting panel or deployment image.

Ask each system owner which version serves production traffic. Include staging and internet-facing development systems in the review. Record the application, host, runtime version, package source and person responsible for the update.

Apply the update and verify service

Use packages from the operating system vendor, hosting provider or official PHP source. Do not copy a package from an unknown site. Follow the provider’s steps to update the runtime, then restart PHP-FPM, web server processes and long-running workers that use the old code.

Check the active runtime after the update. Review service health, application logs and important site functions. If a provider manages the server, ask for the installed package level and the time when all workers were restarted.

Reduce the time between fixes

Keep a current inventory of internet-facing software and assign an owner to each system. Set a process for reviewing vendor advisories, testing urgent changes and confirming that the change reached every environment. A scoped server security assessment can help identify exposed services and weak configurations that patching alone does not address.