Skip to content
CVE-2026-126714: update PHP session runtimes

CVE-2026-126714: update PHP session runtimes

November 21, 2026

PHP disclosed CVE-2026-126714 on November 19, 2026. The PHP CNA record rates it Critical, with a CVSS 4.0 score of 9.2. Update the PHP runtime used by applications that use file-based sessions.

Select the branch update

The corrected releases listed in PHP’s release changelog are:

Maintained branchAffected branch versionsCorrected release
8.2Before 8.2.368.2.36
8.38.3.0 through 8.3.368.3.37
8.48.4.0 through 8.4.278.4.28
8.58.5.0 through 8.5.128.5.13

The CNA’s first affected range also includes older PHP releases. An older, unsupported branch is not cleared by its absence from this maintenance table; plan a supported upgrade with the application’s owner.

For distribution-maintained PHP, check the vendor’s CVE status and exact package revision. A vendor may backport the correction without adopting the upstream version shown above. Retain that evidence with the deployment record.

Replace the application runtime

Inventory the runtime used by each application pool, including workers in containers and scheduled jobs. A command-line PHP installation can differ from the runtime serving the application. Record the executable or image identity and package origin for each deployment.

Preserve a recoverable configuration backup and follow the application’s maintenance procedure. Install the corrected package, or rebuild the application image from a verified corrected runtime. Confirm that the chosen image is actually available before using it; an upstream PHP release does not establish a container tag’s contents.

Restart or replace the application workers through the service’s supported deployment process. Verify that every serving worker uses the intended runtime and that obsolete replicas have left service.

Check normal session behavior

Use an approved test account to perform ordinary sign-in, navigation and sign-out. Confirm that expected session continuity remains intact and review application startup and session-storage errors. Keep test data separate from real users’ session data.

Record the running runtime version and package or image identity alongside the operational result. Normal sign-in is a regression check, not proof of patch coverage by itself.

Acknowledgements

This post was created with assistance from AI.

Last updated on