Skip to content
CVE-2026-129289: update and verify the PHP-FPM runtime

CVE-2026-129289: update and verify the PHP-FPM runtime

November 20, 2026

The PHP Group disclosed CVE-2026-129289 on November 19, 2026 and rates it Critical, with a CVSS 4.0 score of 9.2. Its CNA record identifies the PHP-FPM component and affected release ranges. Whether a deployment is exposed depends on its configuration; the score alone does not establish exposure for every PHP installation.

Select the corrected branch release

Use the correction for the PHP branch you deploy:

PHP branchAffected branch releasesCorrected release
8.2Before 8.2.368.2.36
8.38.3.0 through versions before 8.3.378.3.37
8.48.4.0 through versions before 8.4.288.4.28
8.58.5.0 through versions before 8.5.138.5.13

The CNA record also includes older PHP releases in its affected range. For an obsolete branch, plan a move to a supported corrected release instead of treating its absence from this table as evidence of safety.

For distribution or vendor packages, consult that provider’s security status for the exact package build. A provider can backport a correction without adopting the upstream version number. Preserve the package advisory and installed build as evidence when using that route.

Update the runtime that serves the application

Inventory each PHP-FPM installation, including separate pools served by different runtime packages and container deployments. Identify which service or image actually handles the application’s requests. A command-line PHP installation can differ from the serving runtime.

Back up application configuration and follow the package provider’s supported update procedure. For containers, select a verified corrected image or rebuild with corrected packages when they are available, then replace the running deployment. Pulling an image without replacing its running containers leaves the deployed runtime unchanged.

Restart or replace the affected PHP-FPM workers through the deployment’s normal maintenance process. Preserve service configuration and follow the process for draining traffic where required. Do not assume that replacing files on disk updated processes that were already running.

Verify the completed rollout

Record the installed package or image identity and confirm the serving runtime version through administrative tooling available to the operator. Check every serving instance. Avoid publishing a diagnostic page that exposes runtime or configuration details.

After replacement, check normal application responses and service logs for startup or compatibility errors. Keep those operational checks alongside the corrected package or runtime evidence; ordinary successful requests alone do not prove that the security update is installed.

This update addresses a different CVE from CVE-2026-115560, although the corrected upstream branch releases coincide. An existing maintenance record can cover both only when it proves that the serving runtime received the corrected build.

Acknowledgements

This post was created with assistance from AI.

Last updated on