Check Point Research has confirmed that attackers exploited the PHP2Shell vulnerabilities to break into unpatched Check Point Security Gateways through their Mobile Access portals. The activity began on 30 October 2026, roughly one week after a security fix became available. Check Point published its findings on 12 November 2026.

PHP2Shell is the name for two PHP flaws, CVE-2026-109618 and CVE-2026-109619. As The Hacker News reports, both let anyone run code on the web server without logging in. In the Check Point intrusions, attackers chained them with CVE-2026-123039, a local privilege-escalation flaw, to gain root. The highest CVSS score reported for these CVEs is 9.2. The flaws are being exploited in the wild, although they were not listed in CISA's Known Exploited Vulnerabilities catalogue at the time of writing.

At a glance: PHP2Shell (CVE-2026-109618/109619) + CVE-2026-123039. Critical · highest CVSS 9.2. Exploited: Yes, in the wild (not in CISA KEV yet). Affected: Unpatched Check Point Security Gateways running the Mobile Access portal. What to do: Apply Check Point's security fix, then check gateways for signs of compromise.

What is affected

  • Check Point Security Gateways with the Mobile Access portal exposed and not yet patched.
  • Palo Alto Networks PAN-OS management interfaces exposed to the internet. Palo Alto confirmed exploitation of the same two PHP flaws on 28 October.
  • The sources do not list specific affected or fixed version numbers. Check Check Point's own advisory for your release.

What goes wrong

Many firewalls and VPN appliances run a web portal built on PHP. The PHP2Shell flaws let an unauthenticated attacker run code through that portal. On the Check Point gateways, this gave the attackers the limited rights of the portal's service account.

They then used CVE-2026-123039, a flaw in the gateway's DynamicCLI interface, to raise those rights to root. With full control, they planted PHP webshells in the portal's login page templates and installed a persistent backdoor called TSGA with a hidden proxy component called TSProxy. According to Check Point, TSGA can steal configuration, survive in backups and snapshots, and tamper with firewall logs.

In at least one case, the attackers scanned the internal network from the gateway, moved to a VMware ESXi host over SSH using the vpxuser service account, and ran a wiper called destroy_v6. It left politically themed notes named DREAM_ANNEXATION.txt and explicitly rejected ransom talks.

Why it matters

The first wave on 30 October targeted Israeli organisations and included destructive attacks on some of them. A broader second wave on 2 November hit organisations across multiple countries and sectors, with no evidence of destruction. Check Point saw no clear sector preference. That suggests opportunistic attacks: any exposed, unpatched gateway is a candidate.

The backdoor tools are modified versions of PhiliKit, a framework previously seen in attacks on Ivanti VPN appliances and linked by ESET to the China-nexus group UNC5221. Check Point says it cannot assess the true nature of this operation with high confidence. Possibilities include a single actor, an initial access broker, a false-flag operation, or destruction used as a smoke screen.

The practical point is simpler. A compromised gateway sits at the edge of your network. From there, attackers can reach servers, hypervisors and stored data.

What to do now

  • Apply Check Point's security fix for the Mobile Access portal now if you have not already. Confirm the exact release with Check Point's advisory.
  • If you run Palo Alto firewalls, patch PAN-OS and keep management interfaces off the public internet.
  • Limit internet exposure of VPN and admin portals where you can.
  • Assume compromise if you patched late. Patching does not remove webshells or backdoors already installed.
  • Look in the portal template directory for unexpected files named like zz*.tpl or challenge_render.tpl, and check for /tmp/.up.tpl.
  • Check for /tmp/CPconfigdaemon, a process named slot_CPconfigdaemon, the file /lib/libcpfwcommon.so, a listener on TCP port 11072, or the socket /tmp/.p_sock.
  • Review logs for bursts of Apache/PHP segmentation faults and for connections from 130.94.19.204 or 130.94.19.168.
  • Check ESXi hosts for unusual SSH logins by the vpxuser account.
  • Make sure you have offline backups of virtual machines and configuration, since the wiper targeted ESXi.
  • If you find signs of intrusion, isolate the gateway, rotate credentials it could access and bring in incident response support.

Not sure if this affects you? Talk to us and we will check your sites and servers and plan the update with you.

Sources