APT Exploits PHP2Shell & Fragnesia to Root Firewalls

China-Linked APT Exploits PHP2Shell and Fragnesia to Root Firewalls

CRITICAL
October 28, 2026
October 29, 2026
4m read
Threat ActorVulnerabilityCyberattack

Related Entities(initial)

Products & Tech

CVE Identifiers

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

Full Report(when first published)

Executive Summary

A sophisticated threat actor, assessed to be linked to China, is conducting a targeted campaign against internet-facing firewalls. The attackers are leveraging a potent exploit chain that combines the PHP2Shell remote code execution vulnerabilities (CVE-2026-109618 and CVE-2026-109619) with a Linux privilege escalation flaw dubbed Fragnesia (CVE-2026-46300). This combination enables the Advanced Persistent Threat (APT) group to achieve full root-level control of the devices. Post-exploitation activity includes the installation of PHP root webshells and reverse SSH tunnels to maintain persistent access. The campaign has successfully compromised multiple targets, including at least one firewall belonging to a U.S. government-affiliated entity.


Threat Overview

The campaign demonstrates a methodical approach, beginning with broad reconnaissance and progressively narrowing the target set. The threat actor utilized the Chinese internet asset search engine FOFA to identify approximately 19,000 firewalls from an unnamed vendor. This list was then filtered to focus on devices located in the United States, Japan, Taiwan, and South Korea that were running vulnerable versions of PHP, resulting in a refined list of about 240 high-value targets.

Between October 23 and 24, 2026, the APT group launched automated attacks, successfully compromising 25 of these firewalls. In 24 cases, the attackers deployed a PHP webshell to ensure persistent access. While most compromised devices saw no further activity, the attackers escalated their efforts against two firewalls belonging to a U.S. government-affiliated organization. After one device crashed post-exploitation, the attackers pivoted to the second, where they established a reverse SSH tunnel to solidify their foothold, indicating a more determined objective against this specific target.


Technical Analysis

The attack relies on a three-stage exploit chain to move from external scanning to full system control:

  1. Initial Access - RCE via PHP2Shell: The attackers exploit CVE-2026-109618 and CVE-2026-109619, collectively known as PHP2Shell. These critical vulnerabilities in PHP allow for remote code execution on the targeted firewall, giving the actor an initial foothold on the system as the web server user. This aligns with T1190 - Exploit Public-Facing Application.

  2. Privilege Escalation - Fragnesia: With initial access, the actor then exploits CVE-2026-46300 (Fragnesia), a vulnerability in the Linux kernel, to escalate privileges from the web server user to root. This gives them complete control over the underlying operating system of the firewall. This is a classic example of T1068 - Exploitation for Privilege Escalation.

  3. Persistence - Webshell & SSH Tunnel: To maintain long-term access, the attackers deploy two mechanisms:

    • A PHP root webshell, which allows them to execute commands with root privileges at any time via a hidden web interface (T1505.003 - Server Software Component: Web Shell).
    • A reverse SSH tunnel, which creates a persistent, encrypted outbound connection from the compromised firewall to an attacker-controlled server. This bypasses inbound firewall rules and provides a stable C2 channel (T1090.002 - Proxy: External Proxy).

Impact Assessment

The compromise of a perimeter firewall represents a catastrophic security failure. As the primary boundary between an organization's internal network and the internet, a compromised firewall grants an attacker a powerful position to:

  • Monitor, intercept, or modify all network traffic passing through it.
  • Pivot deeper into the internal network, bypassing other security controls.
  • Use the firewall as a launchpad for attacks against other organizations, obscuring the true origin of the attack.

The targeting of a U.S. government-affiliated organization suggests espionage as a potential motive. The establishment of a reverse SSH tunnel indicates a desire for long-term, stealthy access, likely for data exfiltration or to maintain a foothold for future operations.


IOCs — Directly from Articles

No specific Indicators of Compromise (IOCs) such as IP addresses, domains, or file hashes were mentioned in the source articles.


Cyber Observables — Hunting Hints

The following patterns could indicate related activity:

Type
url_pattern
Value
Web Server Logs
Description
Search for URL patterns associated with PHP2Shell exploits, which may include unusual query strings or POST requests to PHP endpoints.
Type
process_name
Value
Endpoint / Firewall Logs
Description
Look for unexpected child processes being spawned by the firewall's web server process (e.g., httpd, nginx, apache).
Type
network_traffic_pattern
Value
Firewall / NetFlow Logs
Description
Monitor for new, persistent outbound SSH connections (typically on port 22) from the firewall itself to an external, unknown IP address. This could indicate a reverse SSH tunnel.
Type
file_path
Value
Firewall Filesystem
Description
Hunt for newly created PHP files in web-accessible directories, especially those with random names or timestamps inconsistent with legitimate software updates.

Detection & Response

  • Vulnerability Scanning: Immediately scan all internet-facing devices for CVE-2026-109618, CVE-2026-109619, and CVE-2026-46300.
  • Log Review: Analyze web server access logs on firewalls for suspicious requests matching the timeframe of the attack (October 23-24). Scrutinize logs for evidence of the PHP2Shell exploit.
  • Egress Traffic Analysis: Implement Network Traffic Analysis (D3-NTA) to detect anomalous outbound connections from network infrastructure devices. A firewall making an outbound SSH connection is highly suspicious and should be investigated immediately.
  • File Integrity Monitoring: Use File Integrity Monitoring (D3-SFA) on firewall devices to alert on the creation of new files in web directories, which could indicate webshell deployment.

Mitigation

  • Patching: The most critical mitigation is to apply the security updates from the firewall vendor that address these vulnerabilities (D3-SU). Given the active exploitation, this should be treated as an emergency change.
  • Restrict Management Access: Limit access to the firewall's management interface to a trusted, internal management network. It should not be exposed to the internet.
  • Egress Filtering: Configure firewall rules to block all outbound traffic from the firewall itself, except for what is explicitly required for its operation (e.g., NTP, DNS). This can prevent reverse SSH tunnels from being established.
  • Web Application Firewall (WAF): Place a WAF in front of the firewall's management interface (if it must be exposed) to filter for malicious requests that could indicate exploitation attempts.

Timeline of Events

1
October 23, 2026
APT group begins automated attacks against a filtered list of 240 firewalls.
2
October 24, 2026
Attack wave concludes with 25 firewalls compromised and webshells deployed on 24.
3
October 28, 2026
This article was published

Article Updates

October 29, 2026

Palo Alto Networks confirms active exploitation of PHP2Shell/Fragnesia on PAN-OS firewalls, issues urgent warning and hotfixes.

MITRE ATT&CK Mitigations

The primary mitigation is to apply vendor patches for PHP2Shell and Fragnesia immediately.

Mapped D3FEND Techniques:

Implement strict egress filtering to block unexpected outbound connections (like reverse SSH tunnels) from network infrastructure devices.

Mapped D3FEND Techniques:

Restrict access to firewall management interfaces to a dedicated, secure internal network.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

The most urgent and effective countermeasure against this attack chain is to apply the necessary software updates. Organizations using the affected firewall vendor must prioritize the deployment of patches for PHP2Shell (CVE-2026-109618, CVE-2026-109619) and Fragnesia (CVE-2026-46300). Given that these vulnerabilities are being actively exploited by a sophisticated APT, this process should be handled as an emergency change. The patch for the PHP flaws will close the initial access vector, while the patch for the Linux kernel flaw will prevent privilege escalation. This two-pronged remediation effort breaks the exploit chain and is the only way to fully protect against this specific threat. Verification should include not only confirming the patch installation but also running a vulnerability scan post-deployment to ensure the flaws are no longer exposed.

To counter the persistence mechanism used in this attack, organizations should implement strict Outbound Traffic Filtering for all network infrastructure devices, including the firewall itself. A firewall should have a very predictable and limited set of reasons to initiate outbound connections (e.g., to NTP servers, vendor update servers). A default-deny egress policy should be created for the firewall's management and data plane interfaces, with explicit allow rules only for known-good traffic. This would directly block the attacker's ability to establish a reverse SSH tunnel, as the initial outbound connection to the attacker's C2 server would be dropped. This control acts as a critical compensating measure, disrupting the attack chain even if the initial exploitation and privilege escalation succeed.

Timeline of Events

1
October 23, 2026

APT group begins automated attacks against a filtered list of 240 firewalls.

2
October 24, 2026

Attack wave concludes with 25 firewalls compromised and webshells deployed on 24.

Sources & References(when first published)

China-Linked Hackers Exploit PHP2Shell to Root Firewalls
SecurityWeek (securityweek.com) •October 28, 2026

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

APTChinaPHP2ShellFragnesiaZero-DayFirewallWebshellCVE-2026-109618CVE-2026-46300

📢 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.