The PHP security team announced on its official website on November 18, 2026 that it will ship releases fixing vulnerabilities in all supported versions of PHP on November 19. The releases are scheduled between 14:00 and 14:30 UTC, which is 23:00 to 23:30 on the same day in Japan Standard Time (JST). The highest severity among the fixed issues is rated CRITICAL.

Fixes Due Late on November 19, Japan Time

According to the announcement, the releases are part of PHP's regular four-week release cycle and cover every version that is still supported. Technical details of the vulnerabilities and the fixed version numbers will be published alongside the releases.

The team says the issues rated CRITICAL require either a non-default configuration or an uncommon setup. Even so, it is urging users to prepare to upgrade promptly once the releases become available. The pre-announcement does not list CVE numbers or CVSS scores for the individual flaws.

Four Branches Affected: PHP 8.2 Through 8.5

According to the support status published on the official PHP website, four branches are supported as of this writing. PHP 8.1 and older have reached end of life and no longer receive updates from the PHP project.

BranchActive supportSecurity support ends
PHP 8.5Until Dec 31, 2027Dec 31, 2029
PHP 8.4Until Dec 31, 2026Dec 31, 2028
PHP 8.3EndedDec 31, 2027
PHP 8.2EndedDec 31, 2026

PHP 8.2 deserves particular attention, as its security support ends on December 31, 2026. Even after applying this round of fixes, sites on 8.2 will likely need to plan a move to 8.3 or later before the end of the year.

Critical Fixes Already Landed in October

This is not the first critical fix in recent weeks. On October 20, the team pre-announced a CRITICAL security release, and on October 21 it shipped PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Those releases fixed two flaws, CVE-2026-109618 and CVE-2026-109619, both of which could allow remote code execution (RCE) and were rated 9.2 under CVSS v4.0.

The two October flaws affected every PHP installation serving web requests, including PHP-FPM, Apache with modphp, php-cgi, FrankenPHP and LiteSpeed. The risk was highest with modphp, where a demonstrated exploit let an unauthenticated request trigger the attack before any application code ran.

CVE-2026-115560, Flagged in Advance, Is Also Due in the Next Release

On October 23, the team issued an informational advisory about the session upload progress feature (session.uploadprogress). It suggested setting "session.uploadprogress.enabled=0" until the next regular bugfix release to fully protect against an unlikely RCE vector.

Only applications with a specific combination are affected: the configuration sets session.serializehandler to "phpbinary" or "phpserialize", the application switches it to "php" with iniset() before session_start(), and session upload progress remains enabled. Applications that never change the serialize handler at runtime can keep the feature enabled. The team said it would handle the issue in the regular release cycle and publish a full advisory for CVE-2026-115560 with the next release.

November 19 is also the planned release date for PHP 8.6.0. In its November 12 notice for release candidate RC7, the PHP project said the next release would be the first general availability release of PHP 8.6.0.

Server Administrators Should Plan Their Update Now

Anyone running websites or services on PHP should set aside time for testing and maintenance in advance so the update can be applied right after release. Those who rely on PHP packages from a Linux distribution or a hosting provider should also check when their provider plans to ship the fixed builds.

Among the mitigations listed in October, session.uploadprogress.enabled=0 had to be set in php.ini, an FPM pool or the server configuration, not via iniset() or .user.ini. Administrators who applied that setting have been advised to keep it in place.

Our Take

Announcing the severity and the release window ahead of time is welcome, since it gives administrators time to prepare. The fact that the CRITICAL issues require non-default configurations should also reassure many sites.

That said, the two October flaws were serious enough to affect default setups. Seeing another CRITICAL fix just four weeks later clearly adds to the operational burden. Still, administrators may not be able to tell whether their own environment is affected until the details are out. Reading the advisories after release and applying the update as routine maintenance, even if the issues do not appear to apply, seems the safest course.

Summary

The PHP security team will ship fixes that include CRITICAL-rated issues on November 19 between 23:00 and 23:30 JST. The releases cover all supported branches, PHP 8.2 through 8.5, and matter to every administrator running websites on PHP. Details and fixed version numbers will be published alongside the releases.

Sources: