Skip to content
CISA confirms PHP2Shell exploitation as researchers document attacks on 25 firewalls

CISA confirms PHP2Shell exploitation as researchers document attacks on 25 firewalls

Mlq.Ai • November 5, 2026

CISA added both PHP2Shell vulnerabilities to its Known Exploited Vulnerabilities catalog on October 26, with a federal remediation deadline of October 29. [1]

PHP fixed the flaws in versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12. The vulnerabilities affect request-processing paths in PHP itself, with the highest demonstrated risk in Apache mod_php. [2]

Amazon recorded an exploit attempt on October 17, four days before disclosure. Independent researchers later reported successful command execution in honeypots and a campaign that rooted 25 firewall and management servers. [3] [4]

Wiz observed PHP2Shell attempts but said none completed the chain in its telemetry, underscoring that exploit reliability varies by build, SAPI, memory layout and worker configuration. [5]

The PHP2Shell vulnerabilities have moved from an emergency patching story to a confirmed-exploitation incident. The U.S. Cybersecurity and Infrastructure Security Agency added CVE-2026-109618 and CVE-2026-109619 to its Known Exploited Vulnerabilities catalog on October 26, listing both as exploited and setting an October 29 remediation deadline for covered federal agencies. The catalog also requires forensic triage under the agency’s vulnerability-response guidance. [1]

That designation followed evidence from Amazon, independent incident responders and security researchers. Amazon said its MadPot honeypots recorded an exploit attempt on October 17, four days before PHP publicly disclosed the flaws and released fixes. [3]

Two PHP runtime flaws, four patched branches

The vulnerabilities are in PHP’s request-processing engine rather than in WordPress, Drupal or another application built on PHP. CVE-2026-109618 involves out-of-memory handling: under certain conditions, PHP can leave request memory in an invalid state and later process that state during request cleanup. CVE-2026-109619 involves stale global state that can continue pointing to memory released by an earlier request. Both carry a CVSS v4.0 score of 9.2 and can lead to unauthenticated remote code execution. [2]

PHP released versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12 on October 21. The PHP advisory identifies Apache mod_php as the highest-risk deployment because researchers demonstrated an attack that reaches vulnerable code before application-level code runs. It describes PHP-FPM and other server application programming interfaces as requiring separate assessment because exploitability depends more heavily on configuration and application behavior. [2]

PHP says updating to a release containing the fixes is the only complete mitigation. Its October 23 advisory separately recommends setting session.upload_progress.enabled=0 for an unusual configuration involving session serialization and runtime settings. That issue is tracked as CVE-2026-115560 and was not part of the October 21 emergency release. [2]

A related issue was revisited after a 2024 audit

The disclosure history explains why the post-mortem has focused on maintainer awareness. Calif Research said an OSTIF and Quarkslab audit in 2024 rediscovered a related out-of-memory issue. Because exploitation had not been demonstrated at the time, the issue was not fixed. Calif said its 2026 researchers later found additional trigger paths and assembled exploit chains against mod_php and PHP-FPM. [6]

Wiz separately reported discovering a PHP vulnerability on August 19, 2026, confirming unauthenticated remote code execution against Drupal on August 20 and WordPress on August 21. Wiz said it reported the findings to PHP on August 24; PHP acknowledged the reports on September 21 and released fixes on October 21. [7]

The timeline does not establish that maintainers ignored a known working exploit for two years. It shows that a related condition was identified during an audit, remained unresolved while its practical security impact was unproven, and was later connected to a complete attack chain. That distinction is important: the evidence changed from a difficult-to-exploit bug class to demonstrated unauthenticated RCE.

Exploitation is confirmed, but reliability is uneven

Researchers have documented more than scanning. Adel Karimi reported successful command execution against PHP honeypots, including shell launches associated with two source addresses. CISA’s October 26 catalog entry independently records the agency’s determination that both CVEs had been exploited in the wild. [1] [4]

Dream Security and Hunt.io described a separate campaign that chained PHP2Shell with the Fragnesia Linux kernel vulnerability against Palo Alto Networks firewalls. Their reports say the operators rooted 25 firewall and management servers across the United States, Japan, Taiwan and South Korea, then used a reverse SSH tunnel and stolen credentials to move deeper into at least one government-affiliated environment. [8]

That account should not be conflated with a separate Unit 42 report a European government agency. Unit 42 later said it could not confirm that the agency’s initial access was associated with the PHP2Shell CVEs and retracted that attribution. [9]

Wiz also reported seeing PHP2Shell attempts, including public exploit variants, but said none completed the full chain in its honeypots. The company attributed failures to request-size limits, worker pinning, memory-layout differences, PHP builds and extensions. It reported a 67% decline in exposed vulnerable machines after disclosure. [5]

The reports support two conclusions: PHP2Shell has been exploited successfully in at least some environments, and a copied proof of concept is not a universal compromise tool. That gap is a reason to investigate systems exposed before patching, not a reason to defer updates.

What administrators should check

Organizations should inventory PHP embedded in web servers, containers, control panels and network appliances, including systems that are not managed as ordinary application servers. Internet-facing installations should be upgraded to a fixed release or to a vendor backport where an older branch is unavoidable. Canadian government guidance also recommends prioritizing internet-facing systems processing untrusted input and identifying third-party products that bundle PHP. [10]

Amazon recommends beginning retrospective searches on October 17, before the public disclosure date. Defenders should review PHP worker crashes, abnormal multipart requests, unexpected child processes, webshells, reverse tunnels, new SSH keys and changes to firewall or directory-service credentials. [3]

CISA lists ransomware use as unknown. The available evidence does not establish a ransomware campaign, but it does establish enough exploitation to require patching and forensic review, particularly on systems that exposed PHP management interfaces or ran Apache mod_php before October 21. [1]