Over 22.6 million exposed instances
Two critical remote code execution (RCE) vulnerabilities, CVE-2026-109618 and CVE-2026-109619, have been identified in PHP, a foundational technology for a vast portion of the web. Collectively referred to as PHP2Shell, these flaws are rated 9.2 (Critical) under CVSS 4.0, indicating a high potential for exploitation with severe impact. Palo Alto Networks' Unit 42 reports that its Cortex Xpanse platform has identified over 22.6 million internet-exposed instances potentially running vulnerable versions of PHP. Although an initial report suggesting active exploitation in an attack against a European government agency was later retracted, the sheer scale of exposure and the critical nature of the vulnerabilities necessitate immediate action from system administrators worldwide. The primary recommendation is to review the advisory from The PHP Group and patch all affected systems without delay.
CVE-2026-109618 and CVE-2026-109619 are critical vulnerabilities that allow for remote code execution in affected PHP installations. An attacker who successfully exploits these vulnerabilities could gain complete control over the underlying server, enabling them to execute arbitrary commands with the privileges of the web server process. The attack vector is remote and requires no authentication or user interaction, making it highly dangerous.
PHP is a server-side scripting language used in over 75% of all websites whose server-side language is known. It is the backbone for countless applications, websites, and popular Content Management Systems (CMS) like WordPress, Drupal, and Joomla. The widespread deployment of PHP means a vulnerability of this severity has a potentially massive global impact. The CVSS 4.0 score of 9.2 highlights the ease of exploitation and the comprehensive impact on confidentiality, integrity, and availability.
Any system running a vulnerable version of PHP is affected. This includes, but is not limited to:
According to telemetry from Palo Alto Networks Cortex Xpanse, over 22.6 million publicly accessible instances have been identified as potentially vulnerable. This number likely undercounts systems that are not directly internet-facing but could be compromised through other means. Organizations must conduct thorough asset inventories to identify all instances of PHP in their environments, including development, testing, and production systems.
As of the latest update on October 25, 2026, Unit 42 has retracted its earlier report linking these CVEs to a specific compromise of a European government agency. They clarified that while an attack was observed in the context of a vulnerable PHP application, they could not definitively attribute the initial access to the exploitation of CVE-2026-109618 or CVE-2026-109619.
Analyst Assessment: Despite the retraction, the absence of confirmed public exploitation does not diminish the risk. Critical RCE vulnerabilities in ubiquitous software like PHP are prime targets for both opportunistic and targeted attacks. Threat actors are highly motivated to develop exploits for such flaws, and it should be assumed that a functional exploit will become available, if it isn't already in private hands. Defenders should operate under the assumption of active exploitation and prioritize patching accordingly.
A successful RCE attack exploiting these vulnerabilities would grant an attacker significant control over the affected web server. The business impact could be catastrophic and includes:
No specific Indicators of Compromise (IOCs) were provided in the source article.
Security teams may want to hunt for the following patterns which could indicate related malicious activity:
.php files that do not align with legitimate application functionality.sh, bash, powershell.exe, cmd.exehttpd, apache2, nginx, php-fpm).*.php, *.txt, *.gifOrganizations should implement a multi-layered detection strategy:
php -v to identify all systems running vulnerable versions of PHP. Products like Cortex Xpanse can identify exposed assets.Analyst-Assessed MITRE ATT&CK® Techniques:
T1190 - Exploit Public-Facing Application: This is the primary initial access vector.T1505.003 - Web Shell: A common post-exploitation payload to maintain persistence.T1059.006 - Python: While the vulnerability is in PHP, attackers often use other scripting languages post-compromise for execution.T1203 - Exploitation for Client Execution: If the server is used to attack visitors.The most effective mitigation is to patch immediately.
php.ini) to disable unnecessary or dangerous functions that could be abused post-exploitation, such as exec(), shell_exec(), and system().PHP2Shell flaws (CVE-2026-109618/19) now actively exploited, chained with Linux kernel privilege escalation for root access, targeting PAN-OS.
The critical PHP2Shell RCE vulnerabilities (CVE-2026-109618 and CVE-2026-109619) are confirmed to be under active exploitation in the wild. Threat actors are chaining these flaws with a Linux kernel privilege escalation vulnerability to achieve root-level access on compromised systems. Observed targets include internet-exposed Palo Alto Networks PAN-OS management interfaces. This development significantly escalates the threat, requiring immediate patching and securing of management interfaces to prevent full system compromise. Unit 42 has verified these exploitation campaigns.
Article updated to add Palo Alto Networks security advisory and other links.
Product protection section updated.
Additional product protection information added for Advanced Threat Prevention, Cortex Cloud, and Prisma Cloud.
Details on post-exploitation activity were added (this update was later retracted).
The update from October 23 regarding active exploitation was retracted.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.