PHP patches critical security flaws affecting all supported versions
The PHP Foundation is releasing fixes today for critical flaws in all supported PHP versions, a language that runs on about 70 percent of the world's websites.
Key points
- The PHP Foundation is releasing patches on November 19, 2026, for critical vulnerabilities in all supported PHP versions.
- CVE-2026-115560, one of the new flaws, can enable remote code execution but requires non-default configuration to be exploitable, limiting its real-world risk.
- PHP runs on roughly 70 percent of websites, making prompt patching important after back-to-back critical vulnerability disclosures in October and November.
- Suspected Chinese attackers used the October PHP2Shell flaws to gain root access on 25 servers across the US, Japan, Taiwan, and South Korea.
The PHP Foundation warned developers and site administrators on Wednesday that security patches were coming. The fixes cover flaws in all supported PHP versions. PHP runs on roughly 70 percent of the world's websites, according to The Register, making this a broad patch event for the web.
The release is set for November 19, 2026, the PHP Foundation said. The update window runs from 2 p.m. to 2:30 p.m. UTC. The foundation told users to be ready to apply the patches as soon as they land.
What the PHP Foundation announced
Wednesday's advisory confirmed the update will cover security bugs in all supported PHP versions. The PHP Foundation rated the highest-severity new flaws as critical, the top level on the standard scale. At that rating, a successful attack could let an outsider take control of a web server.
The foundation added some reassurance. The critical-rated bugs need either a non-default setting or an unusual application code pattern to become exploitable. A PHP server running standard settings and common application code is not the main target of these specific flaws.
The PHP Foundation urged users to "prepare to upgrade promptly once the releases become available," The Register reported. Security professionals generally recommend patching as soon as updates are tested. That advice holds even when the conditions for an attack are narrow.
How this PHP security flaw triggers
The Register named one of the new vulnerabilities as CVE-2026-115560. It is a remote code execution bug, often shortened to RCE, meaning an outsider could run commands on a server without valid login credentials.
An app must configure its session handler to php_binary or php_serialize, then switch that handler to php at runtime using ini_set(), just before calling session_start(). Session upload progress must also be enabled - this is PHP's default setting, but the PHP Foundation said the full combination of all three conditions is very unlikely in real-world applications.
Elizabeth Barron, executive director of the PHP Foundation, told The Register that "The issue can be mitigated with a configuration setting." The stopgap is to set session.upload_progress.enabled=0 and restart the PHP worker. That step closes the attack path until the official patch is in place.
The October PHP2Shell crisis
Thursday's release follows a busy October for PHP security teams. That month, maintainers pushed out emergency fixes for CVE-2026-109618 and CVE-2026-109619, two flaws known collectively as PHP2Shell. The Hacker News reported that PHP2Shell let attackers run code on a server with no credentials required, via crafted HTTP requests that exposed memory safety problems in the language.
The US Cybersecurity and Infrastructure Security Agency added both PHP2Shell flaws to its known exploited vulnerabilities list on October 26. That list tracks bugs confirmed to be active in real attacks. Its entries carry binding patch deadlines for US federal agencies.
A Hunt.io report on October 30, 2026, found 616 PHP2Shell-related files spread across multiple hosts. Those files included exploit kits, cloned proof-of-concept code, automated scanners, and post-exploitation tools. Underground forum participants were also comparing notes on whether the available exploits worked and what conditions they required.
PHP maintainers also patched a separate critical flaw last month. That vulnerability, CVE-2026-111497, was an out-of-bounds write bug in the Brotli decoder library that could cause arbitrary code execution. It was tracked under the names Node2Shell and Broccoli2Shell, The Hacker News reported.
Why PHP's broad reach makes patching urgent
PHP has powered server-side web development for decades. Content management systems, online stores, and custom business applications all depend on it. When serious flaws surface in PHP, the potential impact extends to millions of servers hosting a wide range of sites.
Two waves of critical vulnerabilities in a single month is unusual even for a broadly deployed language. Security teams managing PHP infrastructure have faced back-to-back patch events since October. There has been little time between rounds to test, deploy, and verify each fix across all affected systems.
November's release follows PHP's regular four-week cycle, so it is not an emergency fix like PHP2Shell was. That schedule gives administrators more time to plan and test before rolling out updates. Even so, the critical rating means teams should move promptly once the packages are released.
Attacks linked to the October PHP flaws
PHP2Shell moved from newly disclosed to actively exploited within days. Suspected Chinese attackers combined those flaws with a Linux kernel privilege-escalation exploit. That pairing gave them root access on 25 servers, with the first confirmed intrusions as early as October 23, The Register reported.
Dream, an Israeli AI cybersecurity firm, tracked the campaign. It hit organizations across the US, Japan, Taiwan, and South Korea. Dream said the attackers likely still hold persistent remote access inside some of the targeted networks.
Once inside, the intruders moved into Active Directory environments and planted backdoors, The Hacker News reported. Palo Alto Networks management interfaces and Check Point Security Gateways were also among the systems reached. CrowdStrike noted that building a single reliable exploit across all affected PHP setups is difficult, which helped slow the initial attack wave.
What administrators and developers should do now
The first priority is confirming that the October PHP2Shell patches are already applied. CISA listed those flaws as actively exploited, and confirmed attacks have occurred. Teams that have not yet patched for PHP2Shell should treat that as the more urgent task before turning to Thursday's new release.
For Thursday's update, the approach is simple. Watch the PHP Foundation's official release channel for the packages to arrive. Apply them as soon as internal testing allows, and restart the PHP worker so any configuration changes take full effect.
People who use websites they do not manage themselves rely on those site operators to act quickly. PHP's wide deployment across web platforms means slow patching on even a fraction of servers can expose many users to risk. Keeping browser software current and using strong, unique passwords is good general practice while server administrators work through the update cycle.
Sources
More from the network
Junious Media Network ↗Yellowjackets Season 4 Is the Show's Final Chapter
Showtime's survival drama Yellowjackets concludes after four seasons, with creators Ashley Lyle and Bart Nickerson saying the story is complete and no spinoff is planned.
junidaily.media ↗S&P 500 Drops Into Correction as AI Stocks Fuel Worst Week in 18 Months
AI-stock losses pushed the S&P 500 down 3.7% Friday, dragging the index into correction territory for the first time since March 2025.
junidaily.media ↗Macy's 100th parade will open with a 10-minute Broadway medley
NBC and Macy's will open the 100th Thanksgiving Day Parade on Nov. 26 at 8:30 a.m. with a 10-minute all-star Broadway medley introduced by Julianne Hough.
junidaily.media ↗Army Delays Iowa Lead Azide Blast After Toxic Plume Concerns
The U.S. Army postponed a controlled detonation of degraded lead azide in Iowa after residents and lawmakers raised safety concerns about a toxic lead plume.
junidaily.media ↗