Pre-announced PHP critical security fixes

PHP has scheduled security releases for November 19, 2026, that fix vulnerabilities in all supported versions, with a highest severity of critical. They're expected to include the fix for CVE-2026-115560, a remote code execution flaw.

Vulnerability

PHP has announced security releases scheduled for Thursday, November 19, 2026, between 14:00 and 14:30 UTC. The releases are part of PHP’s regular four-week release cycle. They address vulnerabilities affecting all supported PHP versions, with a highest severity of critical.

PHP states that the issues rated critical require either non-default configuration or uncommon setups. Technical details and fixed version numbers will be published alongside the releases.

The release is expected to include the fix for CVE-2026-115560, a remote code execution vulnerability first disclosed in PHP’s informational advisory of October 23, 2026. PHP said at the time that it would publish a full advisory for this CVE with the next release. Exploitation requires all of the following:

  • session.serialize_handler is set to php_binary or php_serialize in configuration.
  • The application switches the handler to php at runtime with ini_set() before calling session_start().
  • Session upload progress is still enabled, which is PHP’s default.

This is a scheduled release, not an emergency release of the kind issued for PHP2Shell (CVE-2026-109618 and CVE-2026-109619) on October 21, 2026. CovertSwarm recommends treating it as a priority patching event, to be escalated or de-escalated once PHP publishes its advisories.

CVE and severity

PHP rates the highest-severity issues in these releases critical. The number of vulnerabilities, their CVE identifiers and their CVSS scores haven’t been disclosed.

The one CVE expected in the release is CVE-2026-115560, a remote code execution vulnerability.

Impact

The impact of the undisclosed vulnerabilities can’t be assessed until PHP publishes its advisories.

For CVE-2026-115560, successful exploitation would allow an attacker to execute code with the privileges of the PHP process. Potential consequences include unauthorized access to application data and secrets, modification of website content and deployment of malicious server-side files.

Because the critical issues depend on non-default configuration or uncommon setups, exposure is expected to be narrower than for PHP2Shell. Establish whether your own deployments meet the published conditions before assuming they’re unaffected.

Exploit status

No technical details of the new fixes have been published yet, and there are no reports of the vulnerabilities being exploited. Once the releases are available, the patches can be compared against prior versions, which is likely to accelerate exploit development.

No indicators of compromise specific to the new vulnerabilities have been published.

Affected component and versions

The vulnerabilities affect all supported PHP versions. Fixed version numbers will be published with the releases.

  • PHP 8.5: fixed version to be confirmed. Prepare to update promptly on release.
  • PHP 8.4: fixed version to be confirmed. Prepare to update promptly on release.
  • PHP 8.3: fixed version to be confirmed. Prepare to update promptly on release.
  • PHP 8.2: fixed version to be confirmed. Prepare to update promptly on release. PHP 8.2 reaches end of life on December 31, 2026, so plan migration to a supported branch.
  • PHP 8.1 and earlier: no official release expected. These branches are end of life. PHP hasn’t indicated whether source backports will be provided, as they were for PHP2Shell. Check with your distribution or LTS vendor, or upgrade to a supported branch.

Fix and mitigation

  • Prepare to update PHP promptly. Schedule change windows, confirm ownership and stage testing so the new releases, or equivalent vendor packages, can be deployed soon after publication. Prioritize internet-facing services.
  • Confirm PHP2Shell remediation is complete. Any system still below PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or without an equivalent vendor backport, remains exposed to actively exploited vulnerabilities. Treat it as an emergency.
  • Keep or apply the CVE-2026-115560 mitigation. Set session.upload_progress.enabled=0 in php.ini, the FPM pool or server configuration, and restart every worker. Don’t rely on ini_set() or FPM .user.ini files. Keep the setting in place until the fixed release is deployed and verified.
  • Check for the CVE-2026-115560 preconditions. Review PHP configuration for session.serialize_handler set to php_binary or php_serialize. Search application code, frameworks and third-party packages for runtime changes to that setting.
  • Record non-default PHP configuration. Document non-default INI settings, loaded extensions and SAPI choices across the estate, so exposure can be assessed quickly once PHP names the affected configurations.
  • Restart every PHP worker and service after updating. Confirm that the updated runtime is the one serving requests across all PHP-FPM pools, Apache instances and other SAPIs, not only the command-line installation.
  • Identify unsupported PHP installations. Systems on PHP 8.1 or earlier will need a vendor backport or migration. Where neither is available, consider restricting access to trusted networks.
  • Don’t rely on a WAF for protection. Maintain WAF rules as defense in depth, not as a substitute for the update.
  • Keep monitoring. Maintain the PHP2Shell monitoring already in place. That includes watching for unexpected child processes of php-fpm, php-cgi, httpd or apache2, unexpected executable files in web directories and unusual outbound connections.

References

Official sources:

Third-party analysis:

Unofficial research. This contains exploit code, so don’t run it outside isolated environments: