Back to Insights
  • SMB/SME
  • Enterprise

· ASC Editorial Team

Check Point Gateways Exploited Through PHP2Shell: Patch, Then Hunt

On 12 November 2026, Check Point said attackers had exploited PHP2Shell against its Security Gateways. Between 30 October and 4 November, they used the two flaws, CVE-2026-109618 and CVE-2026-109619, to get into internet-facing Mobile Access portals that hadn't been patched. Check Point had released fixes on 23 October, a week before the attacks began.

Check Point says only a couple of dozen unpatched systems, in a single region, were compromised, and that it told affected customers as the attacks happened. That is a small number. But the way the attacks worked holds a lesson for anyone running a security gateway, whatever the vendor.

PHP2Shell gave the attackers access as the portal's service account. They then used a second flaw, CVE-2026-123039 in the Gaia operating system, to become root. Check Point Research says they planted web shells in the portal's templates, installed a backdoor disguised as a Check Point component, and scanned the network from the gateway. In some cases they moved over SSH to a VMware ESXi host and ran a wiper, which left a note but made no ransom demand. Check Point Research saw the destructive activity in the first wave, against Israeli organisations, and not in a broader second wave on 2 November.

Who was behind it hasn't been confirmed. Check Point Research found tools previously linked to a China-nexus group, but says the evidence doesn't allow it to assess the true nature of the operation with high confidence.

Three steps follow for any organisation that runs Check Point gateways.

First, patch. Check Point recommends installing the November Jumbo Hotfix on all Management Servers and Security Gateways as soon as operationally possible, starting with internet-facing gateways that run Mobile Access. The PHP2Shell flaws affect Security Gateways with the Mobile Access portal from R80 to R82.20, and some Spark firewall versions. The Gaia flaw affects R81.20 to R82.20.

Second, hunt, whether or not you've already patched. A gateway patched after 30 October may have been compromised before the fix went on. Check Point lists what to look for, including PHP session files containing the string upload_progress_pwn, unexpected .tpl files in the portal's templates directory, a process named CPconfigdaemon, and traffic from the scanning addresses it publishes. It also warns that finding nothing doesn't rule out a compromise.

Third, look beyond the gateway. The attackers reached ESXi from the gateway using a vCenter service account. Check whether your gateways can open SSH or management connections to hypervisors or other infrastructure, and whether they need to. A firewall that can reach the systems behind it is a route in as well as a control.

If you find signs of compromise, treat it as an incident. Preserve evidence before you rebuild, and assume that any credentials the gateway held, or could reach, are exposed.

Our earlier article on PHP2Shell covered Palo Alto firewalls. The lesson is the same here: a security appliance runs components you may not think of, and a portal on it that faces the internet needs patching as urgently as the firewall itself.

If one of your gateways had been compromised the week before you patched it, how would you know?

Source: Check Point: Security Advisory: Active Exploitation of PHP2Shell and Local Privilege Escalation

Get Insights by email

A short round-up of new articles every Monday morning. Nothing else.

We only keep your email address, and we don't track opens or clicks. Every email has an unsubscribe link. See our Privacy Notice.