PHP Flags Critical Flaws in All Supported Versions, Patch Due Today
Every supported version of PHP carries security vulnerabilities rated as high as critical, the language’s maintainers said in an advisory Wednesday, ahead of a patch release scheduled for November 19, 2026, between 2 and 2:30 p.m. UTC.

· Originally published by ontime+ · Last verified: 19 Nov 2026

Key Points
- PHP maintainers said a security release due November 19 fixes critical flaws across every supported version.
- The highest-rated issue is a remote code execution bug requiring non-default session configuration.
- The fix lands weeks after PHP2Shell exploitation hit Palo Alto and Check Point management interfaces.
The latest:
Every supported version of PHP carries security vulnerabilities rated as high as critical, the language’s maintainers said in an advisory Wednesday, ahead of a patch release scheduled for November 19, 2026, between 2 and 2:30 p.m. UTC. The maintainers said the release is part of PHP’s regular four-week cycle, and that the critical-rated issues require either non-default configuration or uncommon setups.
Details:
- The release: The maintainers said the update arrives on the project’s standard four-week cadence rather than as an emergency out-of-band fix, and will cover security vulnerabilities affecting all supported PHP branches. Beyond the severity rating, the project did not disclose further specifics about the full set of issues being patched.
- The main flaw: The update is expected to include CVE-2026-115560, a remote code execution vulnerability. According to the advisory, exploitation succeeds only under a narrow set of conditions, which is why the maintainers framed the critical rating as dependent on configurations not shipped by default.
- The conditions: The bug requires an application to set session.serialize_handler to php_binary or php_serialize, then switch the handler to php using ini_set() before calling session_start(). It also requires session upload progress to be enabled, a setting PHP turns on by default.
- The mitigation: Until the next regular bugfix release, users were urged to set session.upload_progress.enabled=0 and restart the PHP worker so the change takes effect. The maintainers advised applying the official updates as soon as they become available.
- Recent history: The advisory comes roughly a month after PHP patched two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, tracked together as PHP2Shell. Both allow unauthenticated remote code execution through specially crafted HTTP requests, according to the project.
- Active exploitation: Those PHP2Shell flaws have since come under limited active exploitation, targeting publicly accessible Palo Alto Networks management interfaces and Check Point Security Gateways. Attackers used that access to strike Active Directory environments and deliver backdoors.
- Exploit ecosystem: In a report published October 30, 2026, Hunt.io said it identified 616 PHP2Shell-related files across multiple hosts, spanning shared exploit kits, cloned proof-of-concepts, custom heap exploits, scanners and post-exploitation tooling. Underground forum participants sought exploits and debated whether circulating PoCs actually worked.
- Vendor assessment: CrowdStrike judged that attackers face real technical limits on scaling the campaign, saying “Exploit developers are unlikely to create a single universal exploit that works reliably across all affected PHP deployments.”
- Another patch: Last month PHP also shipped fixes for a critical Brotli flaw, CVE-2026-111497, known as Node2Shell or Broccoli2Shell, an out-of-bounds write in the decoder library that could result in arbitrary code execution.
Background:
PHP runs a large share of the web’s server-side applications, so flaws in the interpreter reach far beyond the language itself. Its maintainers ship security fixes on a fixed four-week cycle, with out-of-cycle releases reserved for the most urgent cases.
Between the lines:
The emphasis that critical issues need non-default setups narrows the exposed population, but one required condition — session upload progress — is enabled by default, which is why the interim advice targets that setting. The PHP2Shell record is the warning: flaws disclosed a month ago moved from patch to limited exploitation against security appliances, with 616 related files already circulating, per Hunt.io.
What’s next
The release window itself: November 19, 2026, 2 to 2:30 p.m. UTC. Watch whether proof-of-concept code for CVE-2026-115560 surfaces, and whether exploitation follows the PHP2Shell pattern of targeting exposed management interfaces.