Skip to content
CVE-2026-115560: Update PHP and verify running workers

CVE-2026-115560: Update PHP and verify running workers

November 19, 2026

PHP released security updates on November 19, 2026. Its release archive recommends updating each maintained branch, and the PHP changelog records the CVE-2026-115560 fix.

Choose the update for your branch

PHP branchRelease containing the CVE-2026-115560 fix
8.58.5.13
8.48.4.28
8.38.3.37
8.28.2.36

Use the updated release for the application’s branch, or a later supported release that retains the fix. The presence of an older PHP version alone does not establish that a particular application is exposed. Apply the security update through the supported installation method and retain the package or build identifier in the change record.

Distribution and hosting vendors may backport security fixes without adopting the same upstream version number. Check their advisory and fixed package revision for CVE-2026-115560 before deciding that a vendor package is unpatched.

Inventory the runtime that serves the application

Record the PHP branch and package revision for each application host or container. Identify the PHP-FPM service or other web-serving PHP runtime, and include separate command-line runtimes used by scheduled jobs and queue workers. A shell’s default PHP executable may differ from the one serving web requests.

Use the installed package inventory and the version-reporting option of the specific runtime binary. Check the binary selected by the service configuration; do not infer the FPM version from an unrelated CLI installation. Keep version information in administrative records rather than publishing a diagnostic page.

Deploy and replace running workers

Preserve the application configuration and a recovery plan before updating. Install the fixed package through the supported package source. For container deployments, confirm that the chosen updated image is pullable for the required platform before rebuilding and deploying it. Record the resolved image digest; a changed build file alone does not update running containers.

Restart or replace the PHP-FPM workers and other long-running PHP processes using the deployment’s documented procedure. For PHP loaded into the web server, follow that server’s restart procedure. Allow for maintenance or rolling replacement so that existing work can drain safely.

After replacement, confirm the installed runtime version and package revision for every instance, and verify that services started using the updated installation. Run normal application health checks and inspect startup errors. Keep failed instances open in the change record. A rollback that restores an older runtime requires a new patch-status assessment.

Acknowledgements

This post was created with assistance from AI.

Last updated on