PHP Security Team Warns of Critical Vulnerabilities, Urges Users to Prepare for November 19 Update

PHP Vulnerabilities

On November 18th, the PHP security team announced that it will release security updates on Thursday, November 19. The updates will address multiple vulnerabilities affecting all supported PHP branches, with the highest severity rated critical.

PHP says the critical issues require non-default configurations or uncommon setups. The team has also encouraged administrators to prepare to install the updates promptly once they become available.

Currently, CVE-2026-115560 is one of the known issues expected to receive a full advisory in this release. It involves PHP’s session upload progress feature and could create a remote code execution vector under specific conditions.

This article will cover the PHP security vulnerabilities, their technical requirements, the relationship with October’s PHP2Shell flaws, and what administrators should do.

PHP Session Upload Progress Flaw  

When a website visitor uploads a file, PHP’s session upload progress feature allows PHP applications to track the upload’s progress and make that information available to the application through session data.

A good example is an online application that allows users to upload documents or images that might use upload progress information to display how much of a file has been transferred.

This is the relevant PHP configuration setting, which is enabled by default:

```ini
session.upload_progress.enabled = 1
```

The CVE-2026-115560 vulnerability involves an unusual interaction between PHP’s session serialization settings, runtime configuration changes, and session upload progress.

The affected application must:

  • Configure `session.serialize_handler` as `php_binary` or `php_serialize`.
  • Change that setting to `php` at runtime using `ini_set()`
  • Make the change before calling `session_start()`.
  • Leave session upload progress enabled.

Combining all these steps can expose an RCE vector.

The main point is that simply having session upload progress enabled does not automatically make an application vulnerable. If an exploitation is successful, it could allow an attacker to execute code on the affected server under the right conditions.

However, I cannot really describe the issue as a universally exploitable remote code execution flaw.

Why this PHP Security Update Matters

CVE-2026-115560 is part of a wider security release affecting all supported PHP branches. The PHP security team has rated the highest-severity issues as critical, although it has clarified that these issues require unusual configurations or non-default settings.

I would still advise administrators to prepare to update. Even when a vulnerability affects only a specific configuration, organisations may not immediately know whether their applications meet those requirements.

So, it’s very important to understand which vulnerabilities affect your environments and whether the relevant fixes have been installed.

How the PHP security vulnerability follows October’s PHP2Shell Attacks  

This recent announcement is connected to the emergency PHP security updates released on October 21, 2026.

The two vulnerabilities that came up in October are:

  • CVE-2026-109618
  • CVE-2026-109619

These flaws, collectively known as PHP2Shell, could allow unauthenticated remote code execution in affected PHP environments, and both received a CVSS 4.0 score of 9.2.

Attackers were already targeting vulnerable systems, prompting security organisations and hosting providers to introduce emergency protections. Subsequently, CISA added the October vulnerabilities to its Known Exploited Vulnerabilities catalogue.

This doesn’t mean that because attackers exploited PHP2Shell vulnerabilities, they are exploiting CVE-2026-115560 or the other November issues.

What Administrators Should Do Before the Security Updates Arrive  

Now that this security update is coming up, administrators should identify the PHP environments running their websites and applications before the scheduled release. I recommend doing three things:

1. Identify the PHP versions in use.

Check the PHP versions running across production websites, development environments, and containers.

Don’t assume that the version displayed in a hosting dashboard represents every PHP process on the server.

2. Review session upload progress settings.

Administrators should check whether their applications use `session.upload_progress` and whether they make runtime changes to `session.serialize_handler`.

The unusual configuration requirements matter when determining exposure.

3. Prepare for the update.

Review application compatibility, arrange a backup where appropriate, and prepare to install the correct security package once the PHP team publishes it.

You don’t necessarily have to disable upload progress across every PHP installation indiscriminately. PHP’s advisory identifies the issue as dependent on an unusual combination of configuration and application code. This means applications that never change the session serialization handler at runtime can keep the feature enabled.

With cPanel VPS hosting, administrators can manage their hosting environment through a familiar control panel while maintaining access to server configuration and application management tools.

Temporary Mitigation for CVE-2026-115560  

There are certain things administrators can do to reduce exposure while waiting for the official security update.

From PHP’s recommended temporary mitigation, you will have to disable session upload progress if the application meets the vulnerable configuration requirements.

Here’s the configuration directive:

```ini
session.upload_progress.enabled = 0
```

This disables PHP’s upload progress tracking feature.

Administrators should also apply the change through the appropriate PHP configuration file or server-level configuration, depending on their environment.

For PHP-FPM deployments, they should ensure the setting takes effect in the relevant pool configuration and restart the affected workers where required.

Two things you should get clear:

  • Disabling upload progress reduces exposure to the specific vulnerability, but it is not a substitute for the official security update.
  • Applications that depend on upload progress functionality may experience changes in behaviour when the feature is disabled.

How to Install the November PHP Security Updates  

Start by explaining that the PHP security team is scheduled to publish the fixes to this vulnerability on November 19.

Once the updates become available, administrators should consult the official PHP security announcement to identify the fixed versions for their respective PHP branches.

The CVE identifiers disclosed in the release include:

The affected PHP branches The fixed PHP versions
PHP 8.5 8.5.12
PHP 8.4 8.4.27
PHP 8.3 8.3.36
PHP 8.2 8.2.35

The Update Process  

Here are the steps to follow if you want to install the security update:

Step 1: Identify the active PHP installation.

Check which PHP version serves actual website requests. This could be PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, or LiteSpeed.

Step 2: Install the appropriate security update.

Use the official PHP downloads or the operating system’s package manager and vendor repositories to do this.

Step 3: Restart affected services.

Depending on the environment, administrators may need to restart PHP-FPM workers or other PHP processes to load the updated runtime.

Step 4: Verify the installation.

Confirm that the running PHP environment contains the security fixes.

Don’t only check  `php -v`. It may not be enough because the command-line PHP installation might differ from the PHP runtime serving website traffic.

What Managed Hosting and VPS Customers Need to Know  

Hosting providers and customers have their role to play in the hosting environment when it comes to PHP security updates.

A. Managed hosting customers

Hosting providers typically manage the underlying PHP environment and deploy security updates across their infrastructure.

Customers should monitor provider announcements to determine whether their hosting environment has already received the fix or whether they need to take additional action.

If you prefer not to handle every server-level configuration yourself, managed cloud hosting can simplify website and hosting environment management while providing built-in security features.

Also, not every managed hosting provider automatically handles every update. The exact responsibility depends on the hosting agreement and the platform.

B. VPS customers

If you are a customer using self-managed VPS environments, you are generally responsible for maintaining your own PHP installations.

You have to look into the following things:

  • Check the installed PHP version.
  • Install the appropriate security package.
  • Review PHP configuration settings.
  • Restart affected services.
  • Verify the updated runtime.

If all you do is update WordPress, themes, or plugins alone, it will not patch vulnerabilities in the underlying PHP runtime.

Why Regular PHP Security Updates Matter  

PHP security vulnerabilities can affect the underlying runtime security even when a website’s CMS, plugins, and themes are fully updated. This is why administrators should monitor security notices and apply patches promptly.

For now, I would recommend three basic practices:

  • Monitor official PHP security announcements.
  • Maintain an inventory of PHP versions and configurations.
  • Apply security updates and verify that the running services use the patched builds.

Even if critical issues require uncommon configurations, you should still identify your exposure and be ready to install fixes promptly. To stay safe, monitor official PHP security announcements and apply the appropriate updates as soon as they’re available.

Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post

Critical Apache HTTP/2 Vulnerability, CVE-2026-119618

Critical Apache HTTP/2 Vulnerability: How CVE-2026-119618 Puts Web Servers at Risk

Related Posts