Back Darkreading Critical PHP Flaws Allow Code Execution, But Don't Panic 'PHP2Shell'
November's monthly security release patches seven critical PHP flaws that should be addressed ASAP, though experts say exploitability varies and depends heavily on configuration.
The PHP team has released a new security update fixing a wide swath of vulnerabilities and issues, but compared to last month's PHP2Shell chaos, how much these bugs will appeal to attackers is harder to pin down.
That's because, according to PHP's maintainers, the seven issues rated "critical" in the latest monthly security update "require either non-default configuration or uncommon setups." The update, published Nov. 19, affects all supported versions of PHP, and maintainers strongly encourage users to upgrade promptly.
This latest update comes on the heels of threat actors targeting PHP2Shell — a pair of vulnerabilities (CVE-2026-109618 and CVE-2026-109619) capable of remote code execution (RCE) in PHP — en masse. PHP is an open source scripting language common in Web development and present in much of the server infrastructure keeping the Internet afloat. Given PHP's ubiquity, the rush to patch created a fervor across the security industry hardly seen since Log4Shell in 2021 .
Related: Cursor Traces Malicious Claude Code Extensions to Third-Party Breach
PHP versions 8.2 through 8.5 now have patches available through the project's downloads page , in the form of 8.2.36, 8.3.37, 8.4.28, and 8.5.13. 8.6.0; the latest major release of PHP also launched today with fixes included.
Of the dozens of issues accounted for in the changelog , the seven marked critical (CVSS 9.2) on GitHub were: session serializer mismatch RCE flaw CVE-2026-115560; use-after-free via repopulation of last_fatal_error_backtrace global after shutdown flaw CVE-2026-129182; timezone cache use-after-free RCE vulnerability CVE-2026-129496; use-after-free after interrupted session shutdown bug CVE-2026-129481; use-after-free in magic method backtraces RCE bug CVE-2026-129474; PHP-FPM request smuggling through an unread HTTP request body bug CVE-2026-129289; and PHP file-based session handler RCE vulnerability CVE-2026-126714 .
While maintainers included workarounds in most critical advisories (barring CVE-2026-115560), they're considered temporary mitigations, and users should upgrade as soon as they can.
Justin Moore, director of adversary operations at Arctic Wolf, tells Dark Reading that two challenges organizations will run into in patching these issues are business continuity for servers running critical functions and visibility.
"A lot of organizations don’t have a complete inventory of where PHP is running, especially with legacy applications, internally developed Web services, managed hosting environments, or third-party software. It’s baked into CMS platforms, hosting control panels, vendor appliances, and old internal apps," he says. "When a vulnerability is disclosed, the primary challenge is identifying every aspect of the business that is affected. The reality is that Internet-facing PHP systems should move toward the front of the patch queue because attackers have repeatedly demonstrated an interest in rapidly exploiting PHP vulnerabilities when a path to code execution exists."
Related: Grok Bots Attempt to Access Corporate Data Without User Approval
PHP Bugs to Prioritize Patching
Among the critical flaws, there are some experts recommend focusing on first. According to Upwind, which published an analysis of the security release, PHP-FPM bug CVE-2026-129289 is the one to close first, because it "gives an unauthenticated attacker PHP code execution with a single request," with no memory corruption, gadget chain, or race required to exploit. Although Upwind assesses it's the most direct route to code execution, "It does need a front end that reuses FastCGI connections and an application path that opens php://input without reading it to the end."
Upwind also noted that three of the vulnerabilities address gaps introduced by the PHP2Shell fixes last month. "PHP ties CVE-2026-129481 and CVE-2026-129182 to cases the October fix for CVE-2026-109619 did not cover," according to the analysis. "A third, CVE-2026-129474, became remotely reachable through a change introduced in 8.5.12."
Related: F-Secure Identifies 26 Ways AI Can Harm Consumers, and Where to Stop Them
All three depend on specific configurations and versions. CVE-2026-129474 and CVE-2026-129182 are only applicable to PHP 8.5, while CVE-2026-129481 excludes PHP 8.2. CVE-2026-129474 and CVE-2026-129182 both rely on PHP 8.5's fatal error backtrace engine feature, which was introduced with that version; for CVE-2026-129481, the session cleanup behavior it exploits was introduced in PHP 8.3.
Finally, among the other recommendations the analysis makes, one broader tip may ring true for a wide range of PHP-using organizations: "Don't forget container images and appliances that bundle their own PHP build. They need a rebuild or a vendor update."
Meanwhile, WatchTowr's Jake Knott tells Dark Reading that CVE-2026-115560, CVE-2026-126714, and CVE-2026-129289 are the ones the firm expects attackers to go after first.
In any case, while not the same level of emergency as seen last month, users should absolutely apply this latest update as soon as they can.
Everyone's PHP Priorities Will Be Different
Just because a vulnerability is rated critical, that does not necessarily mean it applies to all organizations equally or that threat actors will necessarily target each issue like the PHP2Shell bugs last month.
Knott, who is WatchTowr's head of threat intelligence, says organizations must consider factors such as how a vulnerability is exploited, and how likely real-world exploitation is. And more specifically, whether that organization uses the affected configurations or meets the prerequisites for exploitation. Only then can one determine where attackers have a viable path and how defenders can prioritize securing their environments.
He says the best place to start is with three questions. First, how is PHP being run (be it PHP-FPM, Apache mod_php, php-cgi, or something else)? Second, how are sessions configured, and is session upload progress enabled? And third, what settings is PHP running with, and where are errors being logged?
"Organizations should absolutely take these vulnerabilities seriously, and many of the other critical and high-rated vulnerabilities from this week," Knott says. "There is a stark difference in business-as-usual accelerated patching in response to a critical vulnerability, and panic driven by trivially exploitable default configuration vulnerabilities that typically carry the product2shell monikers, which these aren't."
He adds, "Answers to these questions will quickly rule out many of these vulnerabilities and let organizations patch prioritized sets of assets from a position of understanding and actual risk."
Senior News Writer, Dark Reading
Alex is an award-winning writer, journalist, and podcast host based in Boston. After cutting his teeth writing for independent gaming publications as a teenager, he graduated from Emerson College in 2016 with a Bachelor of Science in journalism. He has previously been published on VentureFizz, Security, Nintendo World Report, and elsewhere.
At Dark Reading, he covers a variety of cybersecurity topics, including the cybercrime ecosystem, open source security, and the intersection between AI and threat actors. In his spare time, Alex hosts the weekly Nintendo podcast, "Talk Nintendo Podcast," and works on personal writing projects, including two previously self-published science fiction novels.
He has received numerous awards, including TechTarget's Writer of the Year in 2022 as well as more than 10 Azbee awards for his reporting between 2022 and today.
Want more Dark Reading stories in your Google results?
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
