Check Point makes firewalls and remote access gateways used by many large organisations. On 12 November 2026 it published research on attacks against its Security Gateways. The attackers used PHP2Shell, which we covered in October, together with a new Check Point flaw. In the first wave, they then wiped data on servers behind the gateway.
What happened
Check Point Research, the company’s threat research team, describes two waves of attacks:
- 30 October 2026: a first wave against organisations in Israel. Some victims suffered destructive activity.
- 2 November 2026: a broader second wave against organisations in several countries and sectors. No destructive activity was reported in this wave.
The attackers got in through the Mobile Access portal, the gateway’s web page for remote access. They used PHP2Shell, two critical PHP flaws (CVE-2026-109618 and CVE-2026-109619). They let an attacker run code without signing in.
They then used CVE-2026-123039, a flaw in a Check Point component called DynamicCLI. Check Point says the service runs with full control of the device (as “root”) and accepts local commands without checking who sends them. That took the attackers from the portal’s own limited account to full control of the gateway. Check Point tracks the flaw in advisory sk1000362. BleepingComputer reports that Check Point saw it exploited against “a couple of dozen customers”.
With full control, the attackers installed web shells and a backdoor. In the first wave, they scanned the internal network and used SSH, a remote administration tool, to reach VMware ESXi hosts. ESXi runs many virtual servers on one machine. On those hosts they ran a wiper, a program that deletes data so it can’t be recovered. A note left behind refused any ransom negotiation.
Check Point says it can’t say with confidence who was behind the attacks.
BleepingComputer reports that Check Point recommends installing the November Jumbo Hotfix on all Management Servers and Security Gateways. It fixes both PHP2Shell and the DynamicCLI flaw. Gateways with Mobile Access portals reachable from the internet come first. If the hotfix can’t go on straight away, Check Point advises stopping the dynamic_server process and preventing it from restarting.
What to do now
A break-in at the gateway can reach the whole network behind it. These RiskWitness Blueprint requirements are the ones this story tests.
- RW-DET-06 Urgent security warnings acted on (Foundation). Sign up to your suppliers’ security warnings and act quickly on any that affect your systems. Check Point Research says a fix was available about a week before the attacks began.
- RW-NET-04 Remote access through one managed gateway (Foundation). The gateway must receive every security update. A remote access portal that falls behind is a door left open.
- RW-DEV-10 Critical weaknesses fixed within 48 hours (Established). This applies to systems reachable from the internet when the flaw is critical or a working exploit exists. Both are true here.
- RW-DET-11 Out-of-the-ordinary activity flagged (Established). Check Point lists signs to look for, such as gaps in firewall logs and SSH from the gateway to ESXi hosts. Patching doesn’t remove an attacker who is already in.
- RW-RES-03 A backup copy attackers can’t reach (Foundation). A wiper is only survivable with a copy kept offline, or one that can’t be changed or deleted.
How RiskWitness helps
“Are we affected?” Assets. Record each gateway as an asset with an owner and where it sits. Note whether its Mobile Access portal is reachable from the internet. Link it to the risks and controls that cover it.
“What is the risk, and who owns it?” Risks. Add a risk that an attacker takes over a perimeter device and reaches internal servers. Give it an owner, score it before and after controls, and choose a treatment. If the hotfix must wait, record a risk acceptance with a reason and an expiry. Outside your tolerance, a named approver signs it off.
“Has anyone got in?” Incidents. If you find any of Check Point’s signs of compromise, record an incident with who is handling it. Link the gateway, the ESXi hosts and the risk. RiskWitness shows which regulators may need telling, with their deadlines.
“What will we change?” Controls and Actions. Add controls for patching, monitoring and offline backups. Map each to the requirements above, and record tests and their results, such as a restore from the offline copy. Give each gap an action with an owner and a due date.
“What do we tell leadership?” Reports. Produce a PDF report or slide deck.
Every step is kept in a history that shows who did what and when, with the old and new values. Nobody can edit or delete it. When leadership, an auditor, a customer or a regulator asks how you handled this, the answer is already written down.
Sources
- PHP2Shell exploitation on Check Point Gateway, Check Point Research, 12 November 2026
- Check Point warns of zero-day flaw exploited for root access, BleepingComputer, 13 November 2026
- Check Point gateways hacked via PHP2Shell to deploy VMware ESXi wiper, BleepingComputer, 13 November 2026
