Skip to main content
CybersecurityVulnerability Management

PHP Foundation Warns of Impending Critical Security Update

People prepare in a software development room with rows of computer servers and workstations in the background.

“The issues rated critical require either non-default configuration or uncommon setups,” the PHP Foundation said in a Wednesday advisory, urging users to “prepare to upgrade promptly once the releases become available.”

The PHP Foundation’s Thursday release window

The PHP Foundation has scheduled a “critical” security update to be published on Thursday between 14:00 and 14:30 UTC, the foundation warned in a short advisory. The foundation did not publish exploit code or full technical details ahead of the release, but it flagged the highest-severity bugs in the package as critical and asked administrators and patch managers to be ready to apply updates promptly.

CVE-2026-115560: a new remote code execution vector — but with caveats

One vulnerability singled out in advance is a remote code execution (RCE) flaw tracked as CVE-2026-115560. The PHP Foundation and its Security Team previously described this identifier as associated with an RCE that “requires a very unlikely combination of configuration and specific PHP application code,” Elizabeth Barron, the foundation’s executive director, told The Register in October. The PHP Security Team initially published only an informational advisory rather than an urgent patch because the issue could be mitigated with configuration changes and was not expected to be exploitable in most deployments.

The foundation’s earlier guidance spelled out the technical conditions that make this vector unlikely: an application would need to set session.serialize_handler to php_binary or php_serialize in its configuration, then switch it at runtime to php with ini_set() before calling session_start(); additionally, the session upload progress feature must be enabled. As a temporary mitigation, the advisory instructed users to “set session.upload_progress.enabled=0 until the next regular bugfix release, to fully protect from an unlikely RCE vector.”

October’s PHP2Shell emergency: immediate context for the new release

The November security release follows a turbulent October, when the community raced to apply emergency fixes for two memory-safety defects collectively dubbed PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Those flaws prompted a widespread patching effort because PHP runs on roughly 70 percent of websites, and the US Cybersecurity and Infrastructure Security Agency (CISA) added both CVEs to its Known Exploited Vulnerabilities catalog on October 26.

Security researchers reported active exploitation during that episode. Dream researchers said suspected Chinese attackers had chained PHP2Shell with a Linux kernel privilege-escalation exploit to obtain root on 25 servers — including Palo Alto Networks firewalls linked to US government-affiliated organizations — as early as October 23. Dream reported that those attackers targeted organizations in the US, Japan, Taiwan, and South Korea and “likely still” have persistent, remote access to some compromised networks.

What this means for patch managers, security teams, and affected enterprises

  • Patch managers: Expect a narrow release window on Thursday between 14:00 and 14:30 UTC and be prepared to test and deploy updates quickly. The foundation’s advisory explicitly urged prompt upgrades once the fixes are published.
  • Security operations teams: Review configurations that touch session.serialize_handler and session upload progress. Where feasible, apply the documented mitigation — setting session.upload_progress.enabled=0 — until the official bugfix is available, as recommended by the PHP Security Team.
  • Enterprises running public-facing PHP sites: Factor the recent PHP2Shell activity into risk assessments. The October attacks demonstrated that memory-safety flaws can be chained to escalate access; even vulnerabilities deemed “unlikely” in practical use warrant attention when the codebase and configuration could meet the exact conditions described by the advisory.

Closing: timing, mitigation, and a narrow window for action

The PHP Foundation’s advisory is short on technical exposition but clear on operational expectations: a critical update will arrive within a tightly bounded half-hour window on Thursday, and administrators should be ready to upgrade. For one newly disclosed RCE, the foundation and its Security Team have already published both a technical description of the necessary configuration circumstances and a concrete temporary mitigation — setting session.upload_progress.enabled=0 — that organizations can apply now. Given how attackers combined earlier PHP flaws with kernel exploits to root devices in October, the prudent response is quiet, targeted, and prompt: verify whether your environment matches the unlikely configuration the foundation described, apply the temporary mitigations where appropriate, and be prepared to install the official fixes when the release drops.

Source: The Register — Get ready for another critical PHP security release to drop