PHP prepares critical security fixes for 19 November

White server chassis with a glass side panel and an inserted blue technical module.

The PHP security team has announced updates for all supported PHP versions, scheduled for 19 November 2026 between 14:00 and 14:30 UTC. The highest stated severity is critical. Exploiting the critical issues requires a non-default configuration or an uncommon setup. [1]

Website owners should contact their technical partner now to establish where PHP is used, who will install the patches and who will test the website afterwards. Full vulnerability details and fixed version numbers will be published with the releases.

What the PHP team has confirmed

The announcement on 18 November covers all branches supported at that time. The releases are scheduled as part of the regular four-week cycle. The team encourages users to prepare to update their environments as soon as the patches become available.

Using PHP alone does not establish whether a particular website is vulnerable. An administrator will need to compare the published exploitation conditions with the running configuration and application code.

The PHP2Shell fixes released in October belong to an earlier release. Installing those fixes does not confirm that the updates scheduled for November have also been installed.

Which websites need checking

The checks are relevant to websites and applications that use PHP. WordPress, for example, uses PHP on the server. Updating the content management system, its themes or plugins does not automatically replace the server's PHP package. Updating that package depends on the hosting environment and its administration arrangements. [2]

In the WordPress dashboard, find the PHP version under Tools → Site Health → Info → Server. Pass this information to the administrator so they can check the specific package and the security patches applied to it.

If one company maintains the website and another manages the server, agree which is responsible for PHP. The website maintenance scope should also identify who will confirm updates and test essential features.

What we know about session vulnerability CVE-2026-115560

On 23 October, PHP published a separate informational advisory about CVE-2026-115560. The vulnerability concerns session handling, which helps an application retain user state between requests. When the specified conditions coincide, it can allow an attacker to execute code remotely on the server. PHP said a full advisory would accompany the next regular release. The advance announcement has not yet named the complete list of vulnerabilities in the November release. [1]

The published description of this session vulnerability requires the following conditions to coincide:

  1. The initial configuration sets session.serialize_handler to php_binary or php_serialize.
  2. The application changes that setting to php through ini_set() before calling session_start().
  3. File upload progress tracking through PHP sessions is enabled, controlled by session.upload_progress.enabled. [3]
CVE-2026-115560 requires an initial session configuration, a runtime change in application code and enabled file upload progress tracking.

These conditions describe CVE-2026-115560 specifically. They cannot rule out the risk from other, as yet unpublished vulnerabilities in the November release.

For this session vulnerability, PHP proposed the temporary mitigation session.upload_progress.enabled=0. An administrator should apply it in the appropriate server configuration and restart the PHP workers. It disables upload progress tracking, so check whether the application uses that feature. PHP says applications that never change the session serialization handler at runtime can leave the feature enabled. [1]

How to prepare for the update

Before installation, have a backup of the website files and database and a clear restoration procedure. If changing PHP branches, test theme, plugin and custom code compatibility in a staging environment. WordPress documentation also recommends updating components and checking compatibility beforehand. [2]

After installing the patches, test the actions that generate sales or enquiries. For an online shop, these might include adding a product to the basket, checkout and order notifications. For a service website, send a controlled form enquiry and check its delivery. Ask the administrator to confirm that the PHP workers serving the website are using the updated package.

If you use PHP 8.2, also plan your next upgrade: official security support for this branch ends on 31 December 2026. Installing the patches for a particular release does not remove the need for ongoing maintenance. [4]

What confirmation to request from your administrator

You can send the following request:

Please check our website against the PHP security release scheduled for 19 November 2026. Specify the PHP version and package serving the site, whether the published exploitation conditions apply, when the patches will be installed and which features will be tested. Once complete, please confirm the installed package and the checks performed.

Sources

  1. PHP project announcements for 2026: the warning on 18 November, the session vulnerability explanation on 23 October and the October release context.
  2. WordPress guidance on updating PHP: finding the version, backups and compatibility checks.
  3. PHP session configuration documentation: the upload progress tracking setting.
  4. PHP version support dates.

About the author

Mantas Jankauskas
Mantas Jankauskas SeoRocket.lt

Specialises in web development, website performance and implementing SEO requirements. He works on technical SEO, migrations and structural changes that affect crawling, indexing, stability and user experience.

Author articles
Next article How server log analysis helps you decide what to fix first Read