← 返回列表

PHP2Shell (CVE-2026-109618 and CVE-2026-109619): Detecting unauthenticated remote code execution in PHP core

单站 Sysdig Blog 发布 Wed, 28 Oct 2026 00:00:00 GMT 入库 2026-11-18T05:37:43

PHP2Shell (CVE-2026-109618 and CVE-2026-109619): Detecting unauthenticated remote code execution in PHP core

Get security briefings from the Threat Research Team

New campaigns, attacker techniques, and detection guidance — straight to your inbox.

Subscribe

Falco Feeds extends the power of Falco by giving open source-focused companies access to expert-written rules that are continuously updated as new threats are discovered.

learn more

Green background with a circular icon on the left and three bullet points listing: Automatically detect threats, Eliminate rule maintenance, Stay compliant, with three black and white cursor arrows pointing at the text.

This blog was originally published on October 22, 2026.

As of October 28, there are four important updates to note:

On October 21, 2026, CVE-2026-109618 and CVE-2026-109619, dubbed PHP2Shell, were fixed in two emergency releases from the PHP project. The two CVEs group four related memory-safety bugs, and both vulnerabilities have a CVSS v4.0 score of 9.2. An unauthenticated attacker can exploit them to run code on a PHP server with HTTP requests alone. Multiple working proof-of-concept (PoC) exploits are circulating, and the researchers who reported the vulnerabilities said AI models helped in both discovery and exploit development.

Researchers reported the bugs to PHP in August 2026, PHP started a coordinated fix in September, and coordinated disclosure was set for October 22. Then, on October 20, the CVE identifiers and exploit details leaked to Hacker News and social media. PHP published an advance notice the same day and moved the release forward by one day, to October 21 at 14:00 UTC.

Exploitation did not wait for the patch. Amazon Threat Intelligence saw a PHP2Shell attempt against its MadPot honeypots on October 17, four days before disclosure. Cloudflare reported early attacks on October 21 at 07:43 UTC, more than six hours before the fix shipped. watchTowr reproduced the bugs and reported active exploitation attempts against each.

The vulnerable code dates back to PHP 5.4, released in 2012. The bugs live in the PHP engine, not within any application. For that reason, any WordPress, Drupal, or Joomla site with clean application code is still exposed.

To provide additional recommendations for security teams and create runtime detection coverage for Sysdig Secure and open source Falco users, the Sysdig Threat Research Team (TRT) analyzed PHP2Shell exploitation. The findings are outlined below.

Affected PHP versions

In addition to the version number, there are three additional factors to consider for potential exposure to PHP2Shell:

Root cause

A PHP worker reuses its memory from one request to another. When a request goes over memory_limit, PHP hits a fatal out-of-memory error and destroys the request heap. The worker survives, and continues to the next request.

The flaw is that PHP does not clear global pointers into the request heap after a fatal out-of-memory error, so a later request on the same worker uses stale pointers into freed memory. All four bugs share this root cause.

CVE-2026-109618: Session upload progress

Session upload progress is enabled by default. It runs during request parsing, before any application code, and even if the application never calls session_start(). Authentication and application filters do not stop it.

CVE-2026-109619: Fatal-error backtrace and OPcache

Impact

PHP2Shell is a pair of unauthenticated remote code execution flaws in the PHP engine itself. Because they sit below the application and trigger before any application code runs, the exposure is every internet-facing PHP server on an affected version, and the impact ranges from silent theft of other users’ secrets to full code execution on the workload, with a path onward to the host.

Detecting PHP2Shell with Sysdig Secure

Sysdig Secure customers using managed policies have detections to help them identify and respond to this active threat. The Sysdig TRT has already published a Threat Intelligence entry for PHP2Shell in Sysdig Secure, and Sysdig vulnerability management detects vulnerable PHP versions across images and hosts. Existing runtime detection rules also cover post-exploitation activity.

Threat intelligence

Sysdig Secure customers already have a PHP2Shell entry in the Threat Intelligence feed. The entry summarizes the flaw, the fixed versions, and the interim mitigations. It also shows how many hosts and workloads in your environment are impacted. Select the count to open a filtered search of the affected asset.

Vulnerability management

Sysdig vulnerability management detects CVE-2026-109618 and CVE-2026-109619 across your environment:

Runtime detection

The Sysdig TRT built two layered runtime rules for PHP2Shell and validated them against a working exploit. They ship as managed rules in the Sysdig Runtime Behavioral Analytics and Sysdig Runtime Notable Events policies. The two rules are PHP Web Worker Killed by Fatal Signal and PHP Web Worker Crash Followed by Shell Execution.

A successful PHP2Shell attack gives the attacker a command line, and from there attackers do what they do after any web RCE. They open a reverse shell, download and run a tool, start a miner, steal cloud credentials, or try a kernel LPE to get root. Sysdig Secure already detects this post-exploitation activity with managed rules in the policies that are enabled by default. Most of these rules match the behavior, not the parent process, so they work the same way whatever PHP runtime serves the application.

Detecting PHP2Shell with open source Falco

Falco sees syscalls, not HTTP requests. It cannot see the malicious request itself, but it can see what the request causes on the host. There are many possible detection strategies, such as detecting shell processes from php workers, but noise often poses a major challenge. As we showed before with Sysdig Secure, many existing post-exploitation detection strategies apply.

Recommendations

Conclusion

PHP2Shell is composed of four memory-safety bugs under two critical CVEs in PHP core, the most widely deployed web runtime. Exploitation began before the fix existed, and PHP has carried the vulnerable code since 2012.

It is the third high-impact flaw this year in old, widely trusted core code, following Copy Fail and Dirty Frag. Like those vulnerabilities, PHP2Shell was found with AI assistance. Defenders should approach these vulnerabilities with an “assume breach” mindset, as exploitation can begin before a patch exists. Patch first. Then, until every worker is patched and restarted, use the interim settings, edge filtering, and runtime detection to close the gap.

原文链接:https://webflow.sysdig.com/blog/php2shell-cve-2026-109618-and-cve-2026-109619-detecting-unauthenticated-remote-code-execution-in-php-core