Another Critical PHP Security Release Lands Thursday: Prepare to Patch
The PHP Foundation will publish a security update on Thursday between 14:00 and 14:30 UTC, and it has warned that the highest-severity bugs in the release are rated critical. In a Wednesday advisory, the foundation urged PHP users to prepare to upgrade promptly once the releases become available.
Few details are public. Unlike last month's PHP2Shell flaws, these vulnerabilities have not leaked. The foundation says the critical issues require either non-default configuration or uncommon setups. One of them is a remote code execution (RCE) flaw tracked as CVE-2026-115560.
That CVE was reserved in October. At the time, the foundation said it did not warrant an emergency fix because exploiting it needs a very unlikely combination of configuration and specific application code. An application must set session.serialize_handler to php_binary or php_serialize, then switch it to php at runtime with ini_set() before calling session_start(). The session upload progress feature must also be enabled. The foundation's interim advice was to set session.upload_progress.enabled=0 until the next regular bugfix release.
The release follows a hectic October, when security teams raced to patch CVE-2026-109618 and CVE-2026-109619, together called PHP2Shell. These memory-safety flaws affect PHP, which runs on about 70 percent of websites. CISA added both to its Known Exploited Vulnerabilities catalog on October 26. Researchers at Dream reported that suspected Chinese attackers chained PHP2Shell with a Linux kernel privilege-escalation exploit to compromise 25 servers from as early as October 23, including Palo Alto Networks firewalls linked to US government-affiliated organisations. Dream said the attackers likely still have persistent remote access.
Why it matters
PHP2Shell showed that fixes get reverse engineered and exploited quickly, so waiting for details to leak is a poor strategy. Any business running PHP sites, including those managed by agencies or hosting providers, is exposed, and the foundation's own wording that critical bugs need unusual setups means exposure depends on configuration you may not have audited. It forces a decision on whether you know where PHP runs and who is responsible for patching it.
What to do
- Apply the PHP update promptly once it is released on Thursday between 14:00 and 14:30 UTC.
- Set session.upload_progress.enabled=0 as an interim mitigation for CVE-2026-115560.
- Check applications for session.serialize_handler set to php_binary or php_serialize and then switched to php with ini_set() before session_start().
- Confirm the PHP2Shell fixes for CVE-2026-109618 and CVE-2026-109619 are already applied.