Live › vulnerability › CVE-2026-115560
Go to dashboardPHP's session upload progress feature has a flaw, which the PHP project disclosed on October 23 in an informational advisory. The sources do not say what an attacker gets from it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-24 17:18 UTC. All times on this page are UTC.
The sources say fully patched PHP releases, including 8.5.12, are affected, so any PHP server with this upload progress feature is in scope. Cloudflare's WAF rule does not cover sites that changed . If a hosting provider manages PHP, ask it to apply the fix.
session.upload_progress.nameNo product ranges from the sources yet.
session.upload_progress.name has been changed from its default in your PHP configuration.php --version; the sources say 8.5.12 is affected.What vendors did on their customers’ behalf. Holds only for traffic through them; patching is still the fix.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
@TheHackersNews · X98 likes · 20 reposts2026-10-23 12:06“The new PHP flaw is separate from the two critical #PHP2Shell bugs patched on October 21. CVE-2026-115560 is NOT fixed by those emergency updates. PHP says exploitation requires an unusual session configuration and considers the risk unlikely in practice. No attacks reported.”
View on X
@TheHackersNews · X63 likes · 13 reposts2026-10-23 12:07“PHP has a one-line mitigation for CVE-2026-115560: session.upload_progress.enabled=0 This disables session upload progress until the fix arrives in a routine release. Already applied this mitigation for CVE-2026-109619? No further action is needed.”
View on X
@TheHackersNews · X55 likes · 10 reposts2026-10-23 12:07“Why isn't PHP issuing another emergency patch? The project considers CVE-2026-115560 unlikely to affect real-world configurations. • No severity score announced • No affected version list yet • Fix planned for a routine release https://t.co/emO9cOJ5Uk”
View on X
Posts are quoted with a link to the original. They are data to us, never instructions.
Cloudflare deploys protections against php2shell vulnerability | Cloudflare Blog
October 21, 2026
Daniele Molteni
Dan Jones
and
Kuber Nandwani
Update - On October 23, the PHP project published an informational advisory for a related vulnerability, CVE-2026-115560, in PHP's session upload progress feature. It affects fully patched PHP releases, including 8.5.12, and will be fixed in PHP's next regular release.
All Cloudflare WAF customers are protected against known exploit attempts if their site uses PHP's default upload progress field name. Customers who have changed session.upload_progress.name are not covered by the WAF rule.
The existing rules "PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #6" protects against this vulnerability.
More information to follow.
October 21, Calif.io, Wiz, OpenAI and Quarkslab disclosed two vulnerabilities in PHP, tracked as CVE-2026-109618 and CVE-2026-109619 and known as php2shell. The vulnerabilities affect all web servers running PHP 5.4 or later and they may allow an attacker to cause denial of service, remote code execution, and data exposure when an application processes specially crafted HTTP traffic.
Cloudflare has been part of a coordinated effort to deploy mitigations to protect the Internet, working with PHP foundation, OpenAI and Wiz among others. Cloudflare has developed and deployed web application firewall (WAF) protections since early October 2026, which were deployed about 9 hours ahead of public disclosure. Starting on October 21 3:02 am UTC, Cloudflare customers using our free or paid WAF were protected by default against php2shell.
Cloudflare successfully deployed multiple mitigations for all its customers while the vulnerability was leaked before the official release date and we observed attack traffic targeting our customers. We observed how attackers were mutating the attack payload to try to bypass our protections by tracking the volume of matches and cross-referencing with the rule logic.
Protecting against php2shell required more than standard request-based rules. Request data alone does not always provide enough evidence to distinguish an exploit from legitimate traffic. The origin’s response adds context, helping identify whether an exploit succeeded while reducing the risk of false positives.
To deliver this protection, we developed full transaction detection, a new Cloudflare WAF capability that combines signals from the request and response within the same HTTP transaction. Response rules can then block a matching origin response before it reaches the requester. The php2shell protections are the first managed detections we have released using this capability.
Customers should patch their PHP repos even with WAF protections providing an additional layer of defense-in-depth mitigation. Our security analysts continue monitoring attack activity and update the rules when and if new techniques and variations emerge in the hours and days ahead. You can track new rules in the changelog.
The protections are available and deployed automatically on all plans with WAF deployed, including Free users.
PHP is used by almost 70% of websites. The php2shell vulnerabilities affect the PHP runtime itself and can allow attackers to execute malicious code on vulnerable servers, expose customer data, or disrupt services. Because PHP underpins widely used platforms such as WordPress and Magento, these flaws could potentially affect a large number of applications across the Internet.
The two vulnerabilities involve how PHP handles memory when something goes wrong while processing a HTTP request. Normally, PHP allocates memory to store the data it needs to process a request, then releases it when that work finishes. If processing stops unexpectedly, for example because it runs out of memory, PHP fails to clean up the memory safely. These vulnerabilities arise when PHP handles an error and then tries to use data that was not fully set up or memory that has already been released.
An attacker can send specially crafted HTTP requests to trigger these conditions. Large requests are one way to put memory under pressure, but the problem goes beyond consuming server resources. By manipulating the data PHP encounters in this invalid memory, an attacker may be able to crash a PHP process, expose sensitive information, or execute code provided by the attacker.
The two vulnerabilities differ in when the unsafe memory access happens:
Vulnerability
What goes wrong
CVE-2026-109618
PHP runs out of memory and interrupts its work before some internal data has been properly initialized. During cleanup of that request, PHP may use this unfinished data as though it were valid.
CVE-2026-109619
A fatal error interrupts a request, leaving PHP holding references to memory that is released when the request ends. When the same PHP process handles a later request, it may follow those outdated references and access memory that is no longer valid and expose sensitive data.
These flaws are in the PHP runtime, so updating website code or a plugin(s) alone does not fix these vulnerabilities. Administrators need to update the PHP software running their applications. If a hosting provider manages PHP, ask the provider to apply the security update.
Administrators can follow the PHP advisory for affected versions and remediation instructions. Keep Cloudflare WAF protections enabled while patching. Restricting unnecessary uploads and limiting upload sizes can also reduce exposure, but these measures do not replace the PHP fix.
For Free customers, new rules have been released under the Cloudflare Managed Free Ruleset (Ruleset ID 77454fe2d30c4220b5701f6fdfb893ba). Free customers don’t have to take any actions to enable the protection. To override the ruleset behavior, you can refer to our documentation.
| Rule Description | Rule ID |
|---|---|
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) | 4e315666e8e344cdb64119a3b5ccf32f |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #2 | 00c10e6cc4da4bd08722adeebcd95984 |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #3 | 48ddf592361e4fdb97a8a85982dab691 |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #4 | 3556683d512a47f2937899c524b1a4c6 |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #5 | da07c85852e34625bb478496302ede46 |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #6 | 19373a83abb840e18ab3ce5a7975ce1b |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #7 | 07f0b6ddaabf40b1b2042dade8d613fa |
Protection for paid plans has been released as part of the Cloudflare Managed Ruleset (Ruleset ID efb7b8c949ac4650a09736fc376e9aee). If you are on a Professional, Business, or Enterprise plan, review your Managed Ruleset deployment to confirm it has deployed block mode.
| Rule Description | Rule ID |
|---|---|
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) | c1d409ad838f47f59446f21cc438d5dd |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #2 | f9a45927414245e3a64bb12d0a0c2f64 |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #3 | 771c654ae1154d4daa72f4e1545d163c |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #4 | 217005865f0145f392300bac212afcc9 |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #5 | 38efdb17ea594501bb55a1d71867b12e |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #6 | 4148ae686fdb4d01be673fab9d9c073d |
| PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619) #7 | 1389aa259617437392ce149c48143645 |
To better identify exploit attempts, Cloudflare developed full transaction detection, a new
This page as .md · .json · in your agent: get_signal("CVE-2026-115560")