As reported by The Hacker News, PHP maintainers have issued an advisory for a critical security release landing November 19, 2026, between 2:00 and 2:30 p.m. UTC. The release patches vulnerabilities across all supported PHP versions, with the highest severity rated CRITICAL. While PHP notes these critical issues require non-default or uncommon configurations, the recent PHP2Shell exploitation pattern demands defenders treat this release as urgent.
Known Vulnerability: CVE-2026-115560
| Field | Detail |
|---|---|
| CVE ID | CVE-2026-115560 |
| Severity | Critical |
| Type | Remote Code Execution (RCE) |
| Affected Software | All supported PHP versions |
| Exploitation Conditions | Application sets session.serialize_handler to php_binary or php_serialize, then switches to php via ini_set() before session_start(); session upload progress enabled (default) |
| Patch Available | Yes — November 19, 2026 release (2:00–2:30 p.m. UTC) |
| Workaround | Set session.upload_progress.enabled=0 and restart PHP workers |
| Active Exploitation | Not yet observed for this CVE; however, related PHP2Shell flaws (CVE-2026-109618, CVE-2026-109619) are under limited active exploitation |
Why This Matters
PHP remains the backbone of roughly three-quarters of the web. Any critical vulnerability in the language runtime itself creates a vast attack surface spanning content management systems, e-commerce platforms, internal applications, and — critically — security appliance management interfaces. The PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) demonstrated this exact risk: threat actors targeted publicly accessible Palo Alto Networks and Check Point management interfaces to pivot into Active Directory environments and deploy backdoors.
The PHP2Shell campaign proved that language-level RCE flaws don't just affect web apps — they become infrastructure attack vectors when appliances expose PHP-based management interfaces.
CrowdStrike's assessment that universal exploits are unlikely across all PHP deployments is accurate but potentially misleading for risk decisions. Even if reliable exploitation requires specific conditions, the sheer volume of PHP deployments means a significant subset will meet those conditions. The session handler configuration required for CVE-2026-115560 is not exotic — many frameworks and applications manipulate session handlers dynamically.
Who Is Most at Risk
ini_set() calls and session configurationsShield53 Recommendations
Immediate Actions (Today)
- Patch immediately: Apply the November 19 PHP security release to all supported versions as soon as it's published (2:00–2:30 p.m. UTC). Do not wait for your distribution's package manager to catch up.
- Audit session configurations: Search application codebases for
ini_set('session.serialize_handler'...andsession_start()patterns. Identify any applications usingphp_binaryorphp_serializehandlers. - Apply workaround where patching is delayed: Set
session.upload_progress.enabled=0inphp.iniand restart all PHP-FPM workers. Document this as a temporary measure. - Inventory PHP versions: Identify all PHP deployments, including those embedded in appliances, containers, and legacy systems. Many organizations will discover PHP versions they didn't know existed.
Short-Term Actions (This Week)
- Review PHP2Shell exposure: If you haven't already, verify that any Palo Alto or Check Point management interfaces exposed to the internet have been patched for CVE-2026-109618/109619. Hunt.io identified 616+ exploit artifacts — assume your perimeter has been probed.
- Deploy WAF rules: Work with your WAF or CDN provider to deploy virtual patches for session-handling anomalies. Look for requests manipulating session handler settings.
- Update detection rules: Add logging alerts for
ini_setcalls targeting session configuration, unexpectedsession_start()behavior, and session upload progress activity on production systems.
Strategic Actions
- Establish PHP version governance: Create an inventory process that tracks PHP versions across all assets, including third-party appliances. Subscribe to PHP security advisories directly.
- Review appliance exposure: Management interfaces should never be internet-facing. Use VPN or zero-trust access for administrative functions, regardless of patch status.
- Plan for Brotli patching: CVE-2026-111497 (Node2Shell/Broccoli2Shell) in the Brotli decoder library was patched last month — verify that all systems using Brotli compression (Node.js, PHP extensions, reverse proxies) have been updated.
The pattern is clear: PHP runtime vulnerabilities are now being actively weaponized against infrastructure targets. Treat today's release as a critical infrastructure event, not a routine developer patch. The gap between advisory disclosure and active exploitation has narrowed significantly — assume adversary scanning begins within hours, not days.