PHP2Shell: Critical RCE Flaws CVE-2026-109618 & CVE-2026-109619

Critical PHP RCE Vulnerabilities (PHP2Shell) Expose Millions of Servers

CRITICAL
October 24, 2026
October 30, 2026
7m read
VulnerabilityPatch ManagementThreat Intelligence

Impact Scope

People Affected

Over 22.6 million exposed instances

Industries Affected

Technology

Related Entities(initial)

Organizations

Palo Alto NetworksThe PHP GroupUnit 42

Products & Tech

Cortex CloudCortex XDRCortex XpansePHPPrisma Cloud

Other

Google

CVE Identifiers

CVE-2026-109618
CRITICAL
CVSS:9.2
CVE-2026-109619
CRITICAL
CVSS:9.2

Full Report(when first published)

Executive Summary

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.


Vulnerability Details

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.

Affected Systems

Any system running a vulnerable version of PHP is affected. This includes, but is not limited to:

  • Standalone web servers running PHP.
  • Servers hosting popular CMS platforms (WordPress, Drupal, Joomla, etc.).
  • Custom web applications built with PHP.
  • Embedded devices or appliances that use PHP for their web interface.

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.

Exploitation Status

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.

Impact Assessment

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:

  • Data Theft: Exfiltration of sensitive data from the server's filesystem or connected databases, including customer information, intellectual property, and credentials.
  • Website Defacement: Altering website content to display attacker-controlled messages, damaging brand reputation.
  • Malware Distribution: Hosting and distributing malware, such as ransomware or banking trojans, to site visitors.
  • Ransomware Deployment: Encrypting server files and demanding a ransom for their release.
  • Lateral Movement: Using the compromised server as a pivot point to attack other systems within the internal network.
  • Resource Hijacking: Using server resources for cryptocurrency mining or to launch DDoS attacks.

IOCs — Directly from Articles

No specific Indicators of Compromise (IOCs) were provided in the source article.

Cyber Observables — Hunting Hints

Security teams may want to hunt for the following patterns which could indicate related malicious activity:

Type
log_source
Value
Web Server Access Logs
Description
Monitor for unusual or malformed POST/GET requests to .php files that do not align with legitimate application functionality.
Type
log_source
Value
Web Server Error Logs
Description
Look for unexpected PHP errors, segmentation faults, or other crashes that could indicate failed exploitation attempts.
Type
process_name
Value
sh, bash, powershell.exe, cmd.exe
Description
Search for shell processes being spawned by the web server process (e.g., httpd, apache2, nginx, php-fpm).
Type
file_name
Value
*.php, *.txt, *.gif
Description
Monitor web-accessible directories for the creation of new files, especially with unusual names or legitimate-looking extensions that contain PHP code (e.g., a web shell).
Type
network_traffic_pattern
Value
Outbound Connections
Description
Baseline normal outbound connections from web servers and alert on new, unexpected connections to unknown IP addresses or on unusual ports.

Detection & Response

Organizations should implement a multi-layered detection strategy:

  1. Vulnerability Identification: Use vulnerability management tools, asset inventory systems, or commands like php -v to identify all systems running vulnerable versions of PHP. Products like Cortex Xpanse can identify exposed assets.
  2. Log Analysis: Actively monitor web server, access, and error logs for signs of exploitation attempts. Implement SIEM rules to detect suspicious request patterns or anomalous responses. This corresponds to D3FEND Network Traffic Analysis (D3-NTA).
  3. Endpoint Detection and Response (EDR): Deploy EDR solutions like Cortex XDR on web servers to monitor for suspicious process execution, such as a web server process spawning a shell. This aligns with D3FEND Process Analysis (D3-PA).
  4. Network Security Monitoring: Use Next-Generation Firewalls (NGFW) and Intrusion Prevention Systems (IPS) with up-to-date signatures to detect and block known exploit patterns at the network perimeter.

Analyst-Assessed MITRE ATT&CK® Techniques:

Mitigation

The most effective mitigation is to patch immediately.

  1. Patching: Update all PHP instances to a version that addresses CVE-2026-109618 and CVE-2026-109619. Refer to the official security advisory from The PHP Group for the latest patched versions and guidance. This is a direct application of D3FEND Software Update (D3-SU).
  2. Web Application Firewall (WAF): As a compensating control, deploy a WAF with rules designed to block attempts to exploit these vulnerabilities. This can provide a layer of defense while patching is underway but should not be considered a substitute for patching.
  3. Restrict Access: Limit administrative access to web servers. Ensure the web server process runs with the lowest possible privileges to minimize the impact of a potential compromise.
  4. Network Segmentation: Isolate web servers from critical internal systems. This can prevent an attacker from moving laterally through the network if a web server is compromised. This aligns with D3FEND Network Isolation (D3-NI).
  5. Configuration Hardening: Review PHP configuration (php.ini) to disable unnecessary or dangerous functions that could be abused post-exploitation, such as exec(), shell_exec(), and system().

Timeline of Events

1
October 21, 2026
Article updated to add Palo Alto Networks security advisory and other links.
2
October 21, 2026
Product protection section updated.
3
October 22, 2026
Additional product protection information added for Advanced Threat Prevention, Cortex Cloud, and Prisma Cloud.
4
October 23, 2026
Details on post-exploitation activity were added (this update was later retracted).
5
October 24, 2026
This article was published
6
October 25, 2026
The update from October 23 regarding active exploitation was retracted.

Article Updates

October 30, 2026

Severity increased

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.

Timeline of Events

1
October 21, 2026

Article updated to add Palo Alto Networks security advisory and other links.

2
October 21, 2026

Product protection section updated.

3
October 22, 2026

Additional product protection information added for Advanced Threat Prevention, Cortex Cloud, and Prisma Cloud.

4
October 23, 2026

Details on post-exploitation activity were added (this update was later retracted).

5
October 25, 2026

The update from October 23 regarding active exploitation was retracted.

Sources & References(when first published)

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

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.

Tags

PHPPHP2ShellPatch ManagementRCEVulnerabilityWeb Security

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

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.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

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 Generator

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.