On 19 November 2026 the PHP project published security releases 8.2.36, 8.3.37, 8.4.28 and 8.5.13 for its existing supported branches, one day after its advance notice of 18 November. They are listed in the PHP release archive and the PHP 8 changelog. PHP 8.6.0 reached general availability the same day. That is a new branch and is not required to patch a site already on a supported branch. This article was checked as of 20 November 2026. Later updates appear in our structured briefing on the PHP November 2026 security releases.

What the selected advisories address

We selected three advisories for site owners to check. The PHP project’s full release notes list more, so treat this as a starting point for a conversation with your provider. Two of the three concern sessions.

CVE-2026-126714 can cause session data loss or corruption, and in some applications code execution. It applies to sessions stored in files, and the default file session handler is within scope. Running file-based sessions does not clear a site, and it does not by itself make a site exploitable. The PHP project’s advisory describes code execution as possible when an attacker can influence the stored session data, a session write is interrupted, and the application contains an object chain that can be abused during deserialization. That is the route the advisory describes; we do not treat the application chain as a requirement for every site. Disabling session upload progress temporarily narrows one path while the update is applied, and it is not a patch.

CVE-2026-115560 is a separate session flaw. It requires session upload progress to be enabled and different serializers handling the same shared session state, and it also needs a suitable object chain in the application before code execution is possible. Separate PHP runtimes can share session storage, which is why a panel, a worker and a website may need to be considered together. Neither issue is the October flaw CVE-2026-109619. Applying the October fix is not evidence that the November fixes are in place.

The third, CVE-2026-129289, affects PHP-FPM when persistent FastCGI connections are reused and the application path leaves a request body unread. Under those conditions unauthorized execution is possible. PHP-FPM deployments that do not meet both conditions are outside that path.

The PHP project notices reviewed here do not establish attacks in the wild for any of the three. Public reporting so far describes discovery and a coordinated fix.

Step one: know which PHP your website actually runs

A small site often has several PHP copies. The website runs under one build, the control panel may ship its own packaged PHP, a cron job or queue worker may use the command line binary, and a container image carries another copy. Each needs its own answer.

The version printed by a command line tool is not necessarily the version serving web requests, and a dashboard label such as PHP 8.3 shows the branch and hides the patch level. Do not publish a phpinfo page to find out, and do not send probes for these CVEs at your own or anyone else’s site. Routine monitoring you already run can continue as normal. For the running version, ask the people who operate the platform.

Step two: questions to put to your provider

  • Which exact PHP release and build serves my website today, and which branch is it on?
  • Is that a build from the PHP project’s source, a distribution package, or a panel-supplied build?
  • Does the running build include the fixes for CVE-2026-126714, CVE-2026-115560 and CVE-2026-129289? If it is a distribution package, which package revision carries the backport, and where can I read that?
  • Are the control panel PHP, any workers or cron jobs, and any containers on separate builds, and what is the status of each?
  • When can the update be applied, and will I be told when the running build has changed?
  • What is the recovery plan if the update breaks something?

Hypothetical reply, upstream branch case

This is an illustration, not a real message. A provider might reply: Your site runs PHP 8.3.36 built from the PHP project’s source under PHP-FPM. We can move it to 8.3.37 promptly. Please tell us a maintenance window that suits you, and we will confirm by email once the running build has been updated. The control panel uses its own packaged PHP, which we are checking separately. That is specific enough to act on. Reply with a window, keep the panel question open, and ask the provider to confirm the running release after the change. For a build on an upstream branch, that confirmation from your hosting provider is the evidence you keep.

Hypothetical reply, distribution and backport case

Also an illustration only. The following quote is fictional and was not written by any real provider: “Your site uses the php8.3 package from Ubuntu 24.04. The version string reads 8.3.6 because Ubuntu carries fixes in its own package versions, so that number alone does not show the patch state. Confirm with us which full package version is installed and that PHP-FPM was restarted after the update.” What the official trackers state as of 21 November 2026 is this. The Ubuntu trackers for CVE-2026-126714 and CVE-2026-129289 list Ubuntu 24.04 Noble php8.3 as fixed in 8.3.6-0ubuntu0.24.04.14 and Ubuntu 22.04 Jammy php8.1 as fixed in 8.1.2-1ubuntu2.29, and each of those package versions fixes those two issues. The tracker for CVE-2026-115560 still lists both packages as needing evaluation, so no fixed version can be named for the third issue yet. The useful facts are the package name, the full package version that fixes each advisory, the tracker status for the one still open, and confirmation that the fixed version is the one actually running. This example covers Ubuntu only. Other distributions and vendors publish their own status, and each must be checked separately.

Step three: have a tested restore path first

Before any update, confirm you have a recent backup and know how to restore it. Test the restore on a staging copy if you can. If the update breaks the service, follow your hosting operator’s protected incident and recovery plan, and have the security impact assessed before the site serves users again. Any recovery decision belongs in that plan, with a record of what was done and when.

Step four: verify after the update

Installing a package is not the same as the website running the fixed code. Processes may need a restart, and a panel may pin a different version per site. After your provider reports completion, check the running release through hosting support or through administrative inventory you trust. Then walk through the workflows that matter: logging in, submitting a form, checking out, uploading a file in the admin area. Keep your normal monitoring and error logs under watch during the rollout and in the period after it, so that problems surface early.

Older branches and what comes next

Sites on PHP branches older than 8.2 are not covered by these releases. They need a supported upgrade plan or clear evidence of a specific vendor backport. Avoid sudden mass changes across many sites at once, and update in small, checked steps. We will record changes in the structured briefing linked above.

Change note, 21 November 2026: the Ubuntu example was updated after a direct reading of the Ubuntu security tracker, which lists fixed Noble php8.3 and Jammy php8.1 package versions for CVE-2026-126714 and CVE-2026-129289 while CVE-2026-115560 remains under evaluation. The file-session paragraph now attributes the deserialization chain route for CVE-2026-126714 to the PHP project’s advisory rather than stating it as a universal requirement. The sources we checked still do not establish real-world exploitation of any of the three issues.