Skip to main content
CybersecurityVulnerability Management

PHP Discloses Critical Flaws, Fixes Slated for November 19

Developer workspace with laptop, tools, and notes on a clean desk near a large window.

November 19, 2026, between 2 and 2:30 p.m. UTC — that is when the PHP maintainers said a security release addressing “CRITICAL” flaws affecting all supported versions will be published.

PHP maintainers' advisory and scheduled release

The maintainers of the PHP programming language on Wednesday issued an advisory announcing an upcoming security release scheduled for November 19, 2026, between 2 and 2:30 p.m. UTC. "These releases are part of PHP's regular four-week release cycle and will address security vulnerabilities affecting all supported PHP versions," the maintainers said. They added that "The highest severity is CRITICAL," while noting that critical-rated issues require either non-default configuration or uncommon setups; no additional technical specifics were disclosed in the advisory.

CVE-2026-115560: reproduction conditions and scope

The advisory is expected to include CVE-2026-115560, described in the public reporting as a remote code execution flaw that succeeds only when a narrow set of conditions are met. Those conditions are explicit: an application must set session.serialize_handler to php_binary or php_serialize in its configuration, and then its code must switch the handler to php with ini_set() before calling session_start(). The second prerequisite is that session upload progress is enabled — the advisory notes that this is PHP's default.

session.upload_progress.enabled mitigation and worker restart

As an immediate mitigation, users were urged to set session.upload_progress.enabled=0 until the next regular bugfix release arrives, and to restart the PHP worker so the setting takes effect. That mitigation targets the known precondition in the expected CVE and is presented as a temporary measure pending the planned release.

Context: PHP2Shell, Brotli fixes, and observed exploitation

The November advisory follows earlier fixes this autumn. Nearly a month prior, PHP released patches for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, collectively tracked as PHP2Shell, which enable unauthenticated remote code execution via specially crafted HTTP requests. Those shortcomings have seen limited active exploitation, where publicly-accessible Palo Alto Networks management interfaces and Check Point Security Gateways were targeted to launch attacks against Active Directory and to deliver backdoors.

Reporting released October 30, 2026, by Hunt.io found 616 PHP2Shell-related files across multiple hosts, “spanning shared exploit kits, cloned proof-of-concepts (PoCs), custom heap exploits, scanners, and post-exploitation tooling,” and noted active discussion in underground forums about exploits and prerequisites. CrowdStrike summarized the exploitation landscape with a technical caution: "Exploit developers are unlikely to create a single universal exploit that works reliably across all affected PHP deployments."

Last month, PHP also released patches for a critical flaw in Brotli — tracked as CVE-2026-111497 and referred to in public reporting as Node2Shell or Broccoli2Shell — an out-of-bounds write in the decoder library that could permit arbitrary code execution. Taken together, these recent patches and advisories show multiple avenues where PHP-related components have required urgent fixes in short succession.

What this means for technologists, affected enterprises, and adversaries

  • Technologists and security teams: Validate whether applications use session.serialize_handler values of php_binary or php_serialize and whether code paths call ini_set() to switch handlers before session_start(). Apply the temporary mitigation by disabling session.upload_progress (session.upload_progress.enabled=0) and restart PHP workers, then plan to install the November 19 release as soon as it becomes available.
  • Affected enterprises and procurement leaders: Inventory externally exposed PHP-powered interfaces and management consoles — particularly publicly-accessible appliances or gateways named in recent exploitation — and prioritize patch windows for systems that match the mitigation conditions described in the advisory.
  • Adversaries and exploit developers: The public record suggests attackers are actively repurposing PoCs and toolkits; however, public comments emphasize the difficulty of creating a single exploit that reliably works across diverse PHP deployments, keeping exploitation likely to remain variant-dependent rather than universal.

The maintainers’ timetable gives administrators a narrow, well-defined window to prepare: apply the temporary configuration change and restart workers now, then install the official fixes when the November 19 release appears. Users were advised to apply the updates as soon as they become available.

Original story