1. Overview
- Article Name: Security advisory: Critical remote code execution vulnerabilities, update now
- Publisher: PHP project
- Published Date: 2026-10-21
- Updated Date: None
- Collection Date: 2026-10-30T08:18:55+09:00
- Original Source: PHP project
- Related Sources: BleepingComputer, PHP OOM advisory, PHP stale-state advisory, Cloudflare, AWS, Wiz, CrowdStrike, Palo Alto Networks, SecurityWeek: Mirai Botnet Operators Join PHP2Shell Attacks as ASLR Bypass Exploits Emerge, Sophos PHP2Shell analysis, VulnCheck PHP2Shell exploit research, SOCRadar exposed attacker tooling, Hunt.io exposed directories analysis, Unit 42: Threat Brief: Critical Vulnerabilities in PHP, CISA KEV: CVE-2026-109618, CISA KEV: CVE-2026-109619, IPA: PHP vulnerabilities (PHP2Shell) alert, BleepingComputer: CISA confirms PHP2Shell exploitation, CISA KEV catalog data, Dream: Chained PHP2Shell exploit roots 25 servers, SecurityWeek: China-linked hackers exploit PHP2Shell to root firewalls, BleepingComputer: Fragnesia in PHP2Shell attacks, CISA 2026-10-28 KEV alert, CISA KEV: CVE-2026-46300, Check Point Research: PHP2Shell exploitation on Check Point Gateway
- Related Malware: TSGA, TSProxy, destroy_v6, gogo
- Related Threat Groups: None
- Related CVEs: CVE-2026-109618, CVE-2026-109619, CVE-2026-46300, CVE-2026-123039
- Related Products and Technologies: PHP 8.2, PHP 8.3, PHP 8.4, PHP 8.5, mod_php, PHP-FPM, php-cgi, FrankenPHP, LiteSpeed, Check Point Security Gateway, Check Point Mobile Access, VMware ESXi, PAN-OS, Panorama, Linux kernel (Fragnesia CVE-2026-46300)
- Response Priority (Author Assessment): Critical
- Rationale for Response Priority: The two PHP2Shell vulnerabilities are rated Critical with a CVSS v4.0 score of 9.2, have no complete alternative mitigations, and are listed in CISA KEV. Exploitation has been confirmed in multiple environments, making it urgent to apply fixes to PHP and appliances incorporating PHP.
- Official Vulnerability Severity (PHP Project): Critical — CVSS v4.0: 9.2 for CVE-2026-109618 and CVE-2026-109619.
2. Quick Summary
PHP2Shell (CVE-2026-109618 / CVE-2026-109619) involves two memory corruption vulnerabilities in PHP core that lead to pre-authentication remote code execution (RCE). Fixed versions are 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35. Exploitation has been confirmed, and these vulnerabilities have also served as entry points into PAN-OS and Check Point Gateway appliances incorporating PHP.
3. Attack Flow
Flow 1 outlines the exploitation mechanism of PHP2Shell. Flows 2 and 3 are separately reported examples of exploitation in the wild.
Flow 1: PHP2Shell Exploitation Mechanism (From Memory Corruption to Pre-Authentication RCE)
- Send a crafted request without authentication to an externally exposed, unpatched PHP execution environment.
- Trigger memory corruption through the misidentification and processing of partially initialized data during OOM handling in CVE-2026-109618, or through the reuse of global state pointing to freed memory in CVE-2026-109619.
- In attacker records recovered by Dream, the attack progressed through memory pressure, a pointer leak via Set-Cookie, and approximately 500MB of additional memory pressure, then invoked zif_system through the pDestructor of a forged HashTable to execute commands with nobody privileges. VulnCheck's research demonstration also confirmed a path to RCE in CVE-2026-109618 using a memory leak.
- Use the acquired execution privileges to deploy a webshell or similar tool and establish a foothold.
Flow 2: Exploitation in the Wild: PAN-OS Management Interface (Reported by Dream)
- According to attacker records recovered by Dream, attackers executed commands with nobody privileges via PHP2Shell in the PAN-OS management application incorporating PHP 8.0.30.
- They chained Fragnesia CVE-2026-46300 to rewrite /etc/pam.d/su, escalate privileges to root, and deploy a webshell. Root access was confirmed on 24 firewalls and 1 internal central management server.
- Only on selected targets did they establish persistence using reverse SSH tunnels and similar methods, pivot to internal central management servers, and enumerate Active Directory using LDAP credentials (whether password spraying, backdoor user or machine account creation, or SAML signing-key extraction succeeded remains unconfirmed).
Flow 3: Exploitation in the Wild: Check Point Gateway (A Case Where the Vulnerabilities Covered Here Served as the Entry Point)
- Check Point observed an initial wave targeting Israeli organizations on October 30, 2026. In this wave, attackers performed unauthenticated code execution via PHP2Shell on the Mobile Access portal and chained CVE-2026-123039 in DynamicCLI to escalate privileges to root.
- They deployed a PHP webshell, TSGA backdoor, and TSProxy, and explored the internal network.
- They moved laterally to ESXi using the vpxuser account used by vCenter for ESXi management and executed the destroy_v6 wiper on some targets (compromise of vCenter itself or the source of the credentials remains unconfirmed).
4. Attacker Position and Execution Location
- An unauthenticated remote attacker reaching an externally exposed PHP execution environment. In the appliance cases, similarly exposed management interfaces and portals served as entry points, and lateral movement utilized root access on the appliances and management accounts such as vpxuser.
5. Visibility for Victims and Administrators
Victim Perspective
- Appears as PHP service crashes, abnormal responses, and tampering via PHP webshells. In the appliance cases, it appears as remote access disruptions, virtual machine shutdowns, political messaging notes left during destructive activity, and ESXi storage destruction.
Administrator Perspective
- Appears as PHP exploit requests, PHP worker crashes, and PHP webshells. In the Check Point Gateway case, DynamicCLI execution, TSGA/TSProxy, gogo scans, vpxuser SSH connections, and destroy_v6 activity are also items to check.
6. Success and Failure Conditions
Success Conditions
- An externally reachable PHP execution environment running unpatched PHP affected by PHP2Shell.
- Conditions that allow memory corruption to progress to code execution. VulnCheck's research demonstration achieved RCE in CVE-2026-109618 even in a production-like x86-64 configuration with ASLR enabled and display_errors disabled.
- In the appliance cases, management applications and similar components incorporating PHP had vulnerable PHP configurations, along with another vulnerability that could be chained to escalate privileges to root (Fragnesia CVE-2026-46300 in PAN-OS and CVE-2026-123039 in Check Point Gateway).
Failure Conditions and Mitigations
- Apply fixed PHP versions (8.5.12 / 8.4.27 / 8.3.36 / 8.2.35 or vendor-provided backported versions) and restart PHP-related workers.
- Apply vendor-specified fixes (such as Check Point hotfixes) to appliances incorporating PHP, and block or restrict external exposure of management interfaces.
7. Impact upon Success
- Attackers can acquire PHP execution privileges without authentication and establish a foothold, such as by deploying a webshell.
- In the appliance cases, root access acquisition, persistent backdoor deployment, internal network scanning, and lateral movement have been confirmed, with some cases resulting in ESXi data destruction and service termination.
8. Observable Logs
- Email: No specific items noted.
- Proxy, SWG, and DNS: PHP2Shell requests targeting public PHP services and management interfaces (verified via PHP service or appliance web access logs, etc.; outbound-only SWG/DNS logs may not capture this).
- Endpoint / EDR: PHP worker crashes and PHP webshells. In the Check Point Gateway case, TSGA, TSProxy, gogo, destroy_v6, and DREAM_ANNEXATION.txt.
- Identity / IdP: ESXi SSH logins using vpxuser (verified via ESXi authentication and execution records; may not appear in IdP logs).
- SaaS / Cloud: No specific items noted.
- Network: External exploit requests targeting public PHP services and management interfaces. In the Check Point Gateway case, internal scans originating from the Gateway, SSH connections to ESXi, and TSProxy tunnels.
9. Attack Success Verification
Attack Attempts Observed (Success Unconfirmed)
- Public Information: AWS observed PHP2Shell exploitation attempts in MadPot on October 17, four days before public disclosure, and on October 21, the day of disclosure. Cloudflare observed attack traffic targeting PHP2Shell and variations of payloads attempting WAF evasion. SOCRadar and Hunt.io identified tooling on public attacker servers and attempts targeting up to 123 hosts, but successful shell acquisition remains unconfirmed. In the Sophos case, the assessment was corrected: the payload did not reach the target, and there was no evidence of successful compromise in customer environments.
- Scope of Confirmation: These observations concern attempts and attack traffic and are not treated as successful compromises. Successful exploitation in real-world environments was unconfirmed in the AWS report. Successful compromises are covered in the individual cases below.
Subsequent Compromise Confirmed (PAN-OS Case)
- Public Information: Command execution with nobody privileges via PHP2Shell, privilege escalation to root and webshell deployment by chaining Fragnesia, and pivoting to internal central management servers and Active Directory enumeration in some environments were confirmed.
- Scope of Confirmation: Assessment based on attacker records recovered by Dream. The scope covers 24 firewalls and 1 internal central management server; activity on 22 machines stopped at webshell deployment. Whether password spraying, backdoor user or machine account creation, or SAML signing-key extraction succeeded remains unconfirmed.
Subsequent Compromise Confirmed (Check Point Gateway Case)
- Public Information: Root access acquisition and backdoor deployment by chaining PHP2Shell with CVE-2026-123039, lateral movement to ESXi, and, on some targets, destructive activity involving deployment of the destroy_v6 wiper and DREAM_ANNEXATION.txt were confirmed.
- Scope of Confirmation: Some of the Gateway compromises investigated by Check Point from October 30, 2026 onward. Destructive activity was confirmed on some targets in the initial wave on October 30, but was not confirmed in the wide-scale scan on November 2.
10. Investigation Playbook
- Trigger: PHP2Shell exploit requests, PHP worker crashes, and webshells. In the appliance cases, Mobile Access PHP errors/exploits, DynamicCLI execution, and ESXi service disruptions.
- Initial Checks: Verify PHP/appliance versions and patch status (including Gateway hotfixes), initial requests, root artifacts, and internal destinations.
- Endpoint: Preserve PHP processes and webshells first, followed by DynamicCLI executions, TSGA/TSProxy, and gogo from the cases.
- Identity and Cloud: Review vCenter, vpxuser, ESXi SSH, and SAML/directory credentials.
- Follow-on Activity: Expand the investigation to other public PHP services, internal scans, ESXi commands, destroy_v6, DREAM_ANNEXATION.txt, and other Gateways.
- Containment: Apply fixed PHP versions and appliance fixes (such as hotfixes), restart PHP-related workers, and proceed with Gateway isolation and rebuilding, credential rotation, and ESXi preservation/recovery.
- Classification: Differentiate between scanning, PHP execution, webshell deployment, root access, backdoors, lateral movement, and wiper deployment.
11. Defense and Detection Ideas
- Single Events: Exploit requests accompanied by PHP worker crashes, PHP webshells, and abnormal DynamicCLI execution, TSGA/TSProxy activity, and destroy_v6 presence confirmed in the cases.
- Time-Series Correlation: Correlate PHP requests -> worker anomalies -> shell deployment -> root access (in the cases) -> internal scans -> vpxuser SSH -> wiper execution.
- Threat Hunting: Search for appliances that remained unpatched in late October 2026 and tooling confirmed in the cases, such as gogo (the start date of hotfix availability has not been verified against the official materials obtained).
- Logging Gaps: Centralize timestamps and request identities across Gateways, vCenters, and ESXi hosts, and store logs externally to guard against log wiping on appliances.
- Priority Controls: Prioritize fixed PHP versions and appliance fixes (such as hotfixes), PHP-related worker restarts, management interface restrictions, vCenter credential rotation, and disabling ESXi SSH.
12. Facts / Inference / Hypothesis
Facts
- The PHP project disclosed two vulnerabilities with a CVSS v4.0 score of 9.2 (Critical).
- CVE-2026-109618 involves a flaw where partially initialized data during OOM handling is incorrectly recognized and processed as valid request data by the cleanup mechanism.
- CVE-2026-109619 is a Use-After-Free issue where global state pointing to freed memory is reused in subsequent requests.
- Fixed versions are 8.5.12, 8.4.27, 8.3.36, and 8.2.35, and no complete alternative mitigations exist.
- VulnCheck successfully demonstrated an RCE exploit utilizing memory leaks for CVE-2026-109618 in a production-like x86-64 configuration with ASLR enabled and display_errors disabled.
- Cloudflare reported observing attack traffic targeting PHP2Shell and payloads attempting WAF evasion (this does not represent confirmation of successful compromises).
- AWS reported observing PHP2Shell exploitation attempts in MadPot on October 17, four days before public disclosure, and on October 21, the day of disclosure. Successful exploitation in real-world environments was not confirmed in this report.
- SOCRadar and Hunt.io identified tooling for PHP 8.4.26 mod_php and attempts targeting up to 123 hosts from public attacker servers, but shell acquisition success was not confirmed.
- Sophos observed PHP2Shell attempts accompanied by Potassium (Mirai-related) payloads, but later corrected that detailed analysis showed payloads did not reach targets and there was no evidence of successful customer compromises.
- Unit 42 retracted its October 23 addendum on October 25, 2026. While compromises were observed in a European government agency within the context of vulnerable PHP applications, it could not be confirmed that initial access stemmed from specific CVEs of PHP2Shell. This incident is not used as backing for PHP2Shell successful compromises or AI involvement.
- The over 22.6 million figure presented by Cortex Xpanse represents public instances identified as potentially vulnerable in telemetry, not confirmed compromises.
- Palo Alto Networks identified PAN-OS and Panorama management HTTPS Web UIs and XML APIs as affected, while GlobalProtect portals/gateways and Captive Portals are not affected. As of October 22, 2026, fixed versions and release schedules were undecided.
- CISA added CVE-2026-109618 and CVE-2026-109619 to its KEV catalog on October 26, 2026, setting a remediation deadline of October 29, 2026, for applicable US Federal Civilian Executive Branch (FCEB) agencies. This is not a universal deadline for general enterprises or globally.
- IPA updated its security advisory on October 27, 2026.
- CISA added Fragnesia (CVE-2026-46300) to the KEV catalog on October 28, 2026, noting in official data that it can be chained with the two PHP2Shell CVEs to deploy PHP webshells and execute commands as root. KEV listing confirms active exploitation but does not newly disclose all steps of chaining or the number of compromised organizations in specific victims.
- Dream confirmed a campaign chaining PHP2Shell and Fragnesia CVE-2026-46300 in PAN-OS management applications incorporating PHP 8.0.30, based on recovered attacker records. Root access was confirmed on 24 firewalls and 1 internal central management server, but activity on 22 machines stopped at webshell deployment, and subsequent activity such as persistence and Active Directory enumeration was limited to selected targets in environments believed to be government-affiliated.
- Dream did not publish the actor's name. China-linked/Chinese-nexus assessments based on Chinese-language environments and tooling do not prove involvement by the Chinese government, and no direct evidence that AI generated exploits or scripts was found.
- Check Point observed an initial wave targeting Israeli organizations on October 30, 2026. In this attack chain, attackers escalated privileges to root by chaining PHP2Shell on the Mobile Access portal with CVE-2026-123039, deployed PHP webshells, TSGA, and TSProxy, and explored the internal network. They then moved laterally to ESXi using the vpxuser account used by vCenter for ESXi management and deployed the destroy_v6 wiper and political messaging notes (DREAM_ANNEXATION.txt) on some targets. Destructive activity was not confirmed in the wide-scale scan on November 2.
- TSGA/TSProxy are modified variants of the PhiliKit family, but Check Point has not attributed this campaign with high confidence. Access to vCenter itself and the source of the vpxuser credentials have not been disclosed, and the exact hotfix availability date and the number of unpatched compromised systems have not been verified against the official materials obtained.
Inference
- When a PHP2Shell compromise is confirmed on an appliance, the investigation needs to track not only the acquisition of PHP execution privileges but also whether privilege escalation and lateral movement occurred, as part of the same incident.
Hypothesis
- No additional hypotheses.
13. MITRE ATT&CK Mapping
| ID | Technique | Confidence | Basis |
|---|---|---|---|
| T1190 | Exploit Public-Facing Application | high | Exploitation prior to authentication against exposed PHP execution environments (Mobile Access portal, PAN-OS management interfaces, etc.) (Check Point Research, Dream). |
14. Unknowns and Further Investigation
- The total number of compromised organizations, the number of destroyed ESXi hosts, and the actor's identity remain undetermined.
- Whether compromises or destructive activity succeeded during the November 2 wide-scale scan has not been confirmed.
15. Impact on SOCs and Organizations
Organizations operating public PHP services or network devices incorporating PHP should avoid relying solely on security products like WAFs and EDRs as permanent solutions, and must apply vendor-supplied patches for PHP and appliances. The target list (240 entries) recovered from attacker records by Dream reportedly included Japanese targets, making it crucial to review external exposure of management interfaces, inspect /etc/pam.d/su and persistence settings, and verify the restart of PHP-related workers.
16. Summary by Role
-
For SOCs: Correlate PHP worker crashes, abnormal HTTP requests/responses, suspicious child processes,
/etc/pam.d/sumodifications, and reverse SSH tunnels. Include pre-disclosure periods in retrospective investigations and evaluate the possibility of memory information disclosure even if RCE is unconfirmed. - For Administrators: Immediately update standalone PHP environments to versions 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35 or vendor-provided backported versions, and ensure PHP worker processes are restarted. For appliances incorporating PHP, apply vendor-specified patches (such as Check Point hotfixes). Restrict external access to appliance management UIs.
- For Users: Follow update instructions if notified by administrators of services you use, and take action only if requested to reset credentials.
Top comments (0)