As reported by SecurityAffairs, the PHP development team has scheduled a critical security release for November 19, 2026, addressing vulnerabilities across all supported PHP versions. The release includes patches for CVE-2026-115560, a remote code execution flaw in PHP's session handling mechanism, and follows closely on the heels of the PHP2Shell emergency patches (CVE-2026-109618 and CVE-2026-109619) released just last month.

Security Impact: As reported by SecurityAffairs, the PHP development team has scheduled a critical security release for November 19, 2026, addressing vulnerabilities across all supported PHP versions.

Vulnerability Overview

CVE IDSeverityDescriptionAffected VersionsPatch Status
CVE-2026-115560CriticalRCE via session handling (requires non-default config: session.serialize_handler set to php_binary or php_serialize, changed to php at runtime via ini_set() before session_start(), with session upload progress enabled)All supported versions prior to November 19 releasePatch available November 19, 2026
CVE-2026-109618CriticalPHP2Shell — unauthenticated RCE via crafted HTTP requestsVersions prior to 8.2.35, 8.3.36, 8.4.27, 8.5.12Patched October 21, 2026
CVE-2026-109619CriticalPHP2Shell — second variant of unauthenticated RCEVersions prior to 8.2.35, 8.3.36, 8.4.27, 8.5.12Patched October 21, 2026

Why This Matters

While the PHP project notes that CVE-2026-115560 requires unusual configurations unlikely to be used in practice, this assessment carries a critical caveat that defenders must internalize: non-default does not mean non-existent. Large enterprises, legacy applications, and frameworks that customize session handling behavior are precisely the environments where unconventional configurations appear — often undocumented and forgotten by the teams that inherit them.

The specific attack chain requires an application to set session.serialize_handler to php_binary or php_serialize, then switch it to php at runtime via ini_set() before calling session_start(), with session upload progress enabled. This is a narrow window — but it's the kind of pattern that emerges in applications that support multiple serialization formats for backward compatibility or session migration purposes.

The convergence of three critical PHP vulnerabilities in under two months signals an elevated threat landscape. Threat actors are actively auditing PHP internals, and the window between disclosure and exploitation is shrinking.

Who Is Most at Risk

  • Custom PHP applications with non-standard session configurations, particularly those handling session serialization format switching
  • Legacy CMS platforms and frameworks that may use non-default session handlers for compatibility
  • Shared hosting environments where tenants may have customized php.ini settings or runtime ini_set() calls
  • Applications still running PHP 7.x or earlier — these versions are end-of-life and will NOT receive patches, creating permanent exposure
  • Organizations that have not yet applied the October 21 PHP2Shell patches — they face compounding risk from both vulnerability sets

Immediate Actions

Immediate Actions
Audit PHP versions across all production, staging, and development environments. Identify any instances still running pre-October 21 patch levels (before 8.2.35, 8.3.36, 8.4.27, 8.5.12).
Inventory session configurations: Search codebases for ini_set('session.serialize_handler', ...) and session.upload_progress references. Any application using both is a priority candidate for immediate post-patch upgrade.
Disable session upload progress as an interim mitigation if your application uses the vulnerable configuration pattern and you cannot patch immediately.
Apply the November 19 release as soon as it becomes available (14:00–14:30 UTC). Given the recent PHP2Shell disclosures, expect PoC development and potential in-the-wild exploitation to follow quickly.
Verify EOL status: Any PHP 7.x or earlier deployments must be prioritized for version upgrade — they will remain permanently vulnerable.

Shield53 Recommendations

The rapid succession of critical PHP vulnerabilities demands a shift from reactive patching to proactive PHP hardening:

  • Establish a PHP version baseline across your entire infrastructure using automated asset discovery. You cannot patch what you cannot see — and PHP installations are frequently shadow-deployed in forgotten corners.
  • Implement configuration drift monitoring for session-related php.ini directives. Flag any runtime ini_set() calls that modify session handling as security-relevant changes requiring review.
  • Maintain a 72-hour patch SLA for PHP critical releases. The October-to-November cadence demonstrates that PHP vulnerabilities now follow the rapid-exploitation pattern seen in other web technologies.
  • Deploy WAF rules that detect session upload progress exploitation attempts and anomalous session cookie structures as a compensating control during the patch deployment window.
  • Plan for PHP 8.x migration if still on 7.x. The security gap between supported and unsupported versions is now existential for internet-facing applications.

The message from the PHP security team is clear: the era of treating PHP as a stable, low-maintenance runtime is over. Organizations must apply the same rigor to PHP patch management that they apply to operating systems and network infrastructure — or accept the consequences of being the next headline.