PHP security releases 8.2.36, 8.3.37, 8.4.28 and 8.5.13 published on 19 November 2026
Identifiers: PHP-November-2026-security-advance · CVE-2026-126714 · CVE-2026-115560 · CVE-2026-129289
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
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 supported branches, one day after its advance notice of 18 November. Three advisories reviewed for this briefing cover two session handling flaws, CVE-2026-126714 and CVE-2026-115560, and one PHP-FPM issue, CVE-2026-129289. Each depends on conditions beyond running an affected version. PHP 8.6.0, released the same day, is a new branch and is not required to patch an existing supported branch. On 21 November 2026 we corrected the Ubuntu packaging status: the Ubuntu security tracker lists fixed php8.3 and php8.1 package versions for CVE-2026-126714 and CVE-2026-129289, while CVE-2026-115560 remains under evaluation for those packages. For deployments that run a vulnerable PHP build behind Cloudflare, its managed rules for two of the three issues are a supplementary layer during and after the update, not a replacement for it. This briefing covers a selection of relevant issues and is not an exhaustive count. The information here was last verified on 21 November 2026.
Impact
Under the conditions each advisory describes, outcomes range from session data loss or corruption to unauthorized code execution. For CVE-2026-126714, the site must store sessions in files, and the default file session handler is within scope. Using it does not clear a site, and using 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; this briefing does not treat the application chain as a requirement for every site. Disabling session upload progress temporarily narrows one path for this flaw while the update is applied, and it is not a patch. For CVE-2026-115560, session upload progress must be enabled, different serializers must handle the same shared session state, and the application must again contain a suitable object chain before code execution becomes possible. For CVE-2026-129289, the PHP-FPM deployment must reuse persistent FastCGI connections and the application path must leave a request body unread. Under those conditions unauthorized execution is possible.
Who is affected
Websites running upstream PHP 8.2.x below 8.2.36, 8.3.x below 8.3.37, 8.4.x below 8.4.28 or 8.5.x below 8.5.13. Distribution and vendor packages carry their own version labels, so upstream version numbers do not describe their patch state. When read directly on 21 November 2026, the Ubuntu security tracker listed CVE-2026-126714 and CVE-2026-129289 as fixed in php8.3 8.3.6-0ubuntu0.24.04.14 for Ubuntu 24.04 Noble and in php8.1 8.1.2-1ubuntu2.29 for Ubuntu 22.04 Jammy, with CVE-2026-115560 still needing evaluation for both packages. Those entries say nothing about other November advisories, and they do not show whether a given server has installed the fixed package version and restarted its PHP services. The status of other distributions and vendors must be confirmed with each of them. Older unsupported upstream branches are not covered and need a supported upgrade plan or evidence of a specific vendor backport. Separately packaged control panel PHP, worker runtimes and container images must each be checked on their own. A deployment that runs a vulnerable PHP build behind Cloudflare remains in scope, because the managed rules inspect only traffic routed through Cloudflare and do not change the PHP build.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| PHP file session handler (CVE-2026-126714) | Upstream 8.2.x <8.2.36, 8.3.x <8.3.37, 8.4.x <8.4.28, 8.5.x <8.5.13 (selected advisories) | 8.2.36, 8.3.37, 8.4.28 and 8.5.13 respective upstream branches; distribution, panel and bundled builds require their own evidence |
| PHP session serialization (CVE-2026-115560) | Upstream 8.2.x <8.2.36, 8.3.x <8.3.37, 8.4.x <8.4.28, 8.5.x <8.5.13 (selected advisories) | 8.2.36, 8.3.37, 8.4.28 and 8.5.13 respective upstream branches; distribution, panel and bundled builds require their own evidence |
| PHP-FPM (CVE-2026-129289) | Upstream 8.2.x <8.2.36, 8.3.x <8.3.37, 8.4.x <8.4.28, 8.5.x <8.5.13 (selected advisories) | 8.2.36, 8.3.37, 8.4.28 and 8.5.13 respective upstream branches; distribution, panel and bundled builds require their own evidence |
Exploitation evidence
Exploitation not established. The PHP project notices reviewed for this briefing do not establish attacks in the wild for CVE-2026-126714, CVE-2026-115560 or CVE-2026-129289. Public reporting so far describes discovery and coordinated fixes. These issues are distinct from the October flaw CVE-2026-109619, and evidence about that issue does not transfer to the November fixes.
Actions
- Confirm with your hosting provider or trusted administrative inventory which exact PHP release and build serves the website, and whether it is an upstream build, a distribution package or a panel-supplied build.
- For upstream builds, update to 8.2.36, 8.3.37, 8.4.28 or 8.5.13 as published by the PHP project on 19 November 2026, and confirm through your hosting provider that the updated build is the one serving the website.
- For distribution or vendor packages, rely on the vendor tracker, because the upstream version number does not describe the package's patch state. For Ubuntu, as of 21 November 2026, php8.3 8.3.6-0ubuntu0.24.04.14 on Ubuntu 24.04 Noble and php8.1 8.1.2-1ubuntu2.29 on Ubuntu 22.04 Jammy fix CVE-2026-126714 and CVE-2026-129289, while CVE-2026-115560 is still under evaluation for both. Ask your provider to confirm that the installed package version is at least the listed one, that PHP services were restarted afterwards, and that they will tell you when Ubuntu resolves the remaining advisory.
- Check control panel PHP, worker and cron runtimes, and container images separately, since each may run a different build and separate runtimes can share session storage.
- Confirm a tested backup and restore path before updating. 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.
- After the update, verify the running release through hosting support or trusted inventory and not through a public phpinfo page, test key workflows such as login, forms, checkout and admin uploads, and keep normal monitoring in place during and after the rollout.
- Plan a supported upgrade for sites on branches older than 8.2, or obtain evidence of a specific vendor backport.
- If your traffic is routed through Cloudflare and the site runs a vulnerable PHP build, treat Cloudflare's managed rules as a supplementary layer while the PHP update is rolled out and after it is in place, not as a replacement for it. Cloudflare's notice of 20 November 2026 states that its Free managed ruleset blocks known HTTP patterns for CVE-2026-126714 by default, while on paid plans coverage depends on the Cloudflare Managed Ruleset being deployed and on the rule's effective action. Its separate rule for CVE-2026-129289 on Pro, Business and Enterprise defaults to Log, which records matching requests without blocking them. Ask whoever manages your Cloudflare account which rules are active and what action each takes. These rules do not fix PHP, do not cover internal paths, and do not protect connections that reach the origin without passing through Cloudflare.
Unknowns
- Whether distribution and vendor packages other than Ubuntu carry these fixes, and when Ubuntu will resolve CVE-2026-115560, which its tracker still listed as needing evaluation for Noble php8.3 and Jammy php8.1 on 21 November 2026.
- For CVE-2026-126714, whether a given site stores sessions in files, whether an attacker could influence the stored session data and interrupt a write, and whether the application contains an object chain of the kind the PHP project's advisory describes.
- For CVE-2026-115560, whether session upload progress is enabled, whether different serializers handle the same shared session state, and whether the application contains a suitable object chain for code execution.
- For CVE-2026-129289, whether a given PHP-FPM deployment reuses persistent FastCGI connections with an unread request body in its application path.
- Patch status of separately packaged control panel PHP and container images.
- For vulnerable deployments behind Cloudflare, whether all traffic actually passes through Cloudflare, whether the Managed Ruleset is deployed on a paid plan, and whether the CVE-2026-129289 rule has been changed from its default Log action to one that blocks.
- Whether advisories beyond the three reviewed here apply to a specific site, since this briefing is a selection and not an exhaustive count.
Sources
- PHP project https://www.php.net/archive/2026.php#2026-11-18-1
- PHP project https://www.php.net/archive/2026.php#2026-11-19-1
- PHP project https://www.php.net/ChangeLog-8.php
- PHP project https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp
- PHP project https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx
- PHP project https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6
- Canonical https://ubuntu.com/security/CVE-2026-126714
- Canonical https://ubuntu.com/security/CVE-2026-129289
- Canonical https://ubuntu.com/security/CVE-2026-115560
- Cloudflare https://blog.cloudflare.com/phpaftershell-waf-protection/
Change history
- — Published: 19 November 2026: Published briefing for the PHP advance notice posted 18 November 2026 announcing critical security releases scheduled for 19 November 2026, 14:00–14:30 UTC.
- — Updated: 20 November 2026: Updated after the PHP project released 8.2.36, 8.3.37, 8.4.28 and 8.5.13 on 19 November 2026, superseding the pre-release information from the 18 November advance notice and adding details for CVE-2026-126714, CVE-2026-115560 and CVE-2026-129289, including that the default file session handler is within scope.
- — Correction: 21 November 2026: Corrected the Ubuntu status after reading the Canonical tracker directly. CVE-2026-126714 and CVE-2026-129289 are listed as fixed in Noble php8.3 8.3.6-0ubuntu0.24.04.14 and Jammy php8.1 8.1.2-1ubuntu2.29, while CVE-2026-115560 remains under evaluation for those packages. Attributed the deserialization chain route for CVE-2026-126714 to the PHP project's advisory instead of stating it as a universal requirement, without adding new chain details, and removed references to secondary research. Noted Cloudflare's 20 November 2026 managed rules as a supplementary layer during and after the PHP update for vulnerable deployments behind Cloudflare.