🔍 Read the full analysis: How To Assess PHP2Shell And Wiper Risks On Check Point Gateways on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Check Point says attackers compromised a small number of unpatched Security Gateways from October 30 to November 4, using PHP2Shell flaws and a separate root-access vulnerability. Some intrusions reached VMware ESXi hosts and ran a destructive wiper; the company’s November Jumbo Hotfix addresses the vulnerabilities, and CISA set a November 16 deadline for U.S. federal agencies to act on the root flaw.
Check Point says attackers compromised a couple of dozen unpatched Security Gateways between October 30 and November 4 by exploiting PHP2Shell vulnerabilities and a separate flaw that gave them root access. In some cases, the attackers moved to VMware ESXi servers and ran a wiper that destroys files; Check Point says it has issued fixes in its November Jumbo Hotfix.
In its November 12 investigation, Check Point described attacks against gateways’ Mobile Access portals. The attackers first used two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, to execute code through the portal. They then exploited CVE-2026-123039, a separate vulnerability in the Gaia operating system, to gain root privileges. Check Point said the observed compromises affected “only a couple of dozen unpatched systems, in a single region.”
Check Point reported that the first wave targeted Israeli organizations. In some of those incidents, attackers reached a VMware ESXi host and ran a wiper called destroy_v6, which overwrites files with zeros before deleting them by default. The program left a note named DREAM_ANNEXATION.txt that, according to Check Point, “explicitly rejects ransom negotiations.” A second wave on November 2 targeted organizations in multiple countries; Check Point said it found no evidence of destructive activity in that wave.
The vendor recommends installing its November Jumbo Hotfix on all Management Servers and Security Gateways, prioritizing internet-facing Mobile Access portals, and checking exposed devices for signs of compromise. Minimum cited releases are Take 14 for R82.20, Take 52 for R82.10, Take 132 for R82 and Take 174 for R81.20. Check Point says versions R81.10 and older are past end of support. CISA added the root-access flaw to its Known Exploited Vulnerabilities catalog on November 13 and set November 16 as the deadline for U.S. federal agencies to act.
Check Point gateway attacks · Oct 30 – Nov 4, 2026
How the break-in worked, and where the fix cuts it
The attack chain as Check Point describes it, without the technical recipe. One update closes the first two doors.
Path through the network (schematic)
InternetAttacker traffic
Gateway web portalMobile Access
Gateway systemRoot rights
Internal networkScanned from the gateway
VMware ESXi hostRuns virtual machines
normaltaken overwipedclosed by fix
Step by step
- Scanfrom Oct 30Unpatched gateways with an internet-facing Mobile Access portal are probed
- Way inPHP2Shell (CVE-2026-109618, CVE-2026-109619) runs code as the portal’s service account closed by fix
- RootCVE-2026-123039 in DynamicCLI turns that into full root rights closed by fix
- Back doorWeb shells in the portal’s login-page folder; TSGA back door with TSProxy hidden in appliance processes
- ReconThe gogo scanner maps internal systems from the gateway
- WipeSSH to a VMware ESXi host, destroy_v6 wiper, a note that rejects ransom talk (first wave, some victims)
R82.20 from Take 14 · R82.10 from Take 52 · R82 from Take 132 · R81.20 from Take 174. It closes both PHP2Shell and CVE-2026-123039. Then check for signs of compromise.
Sources: Check Point Research, “PHP2Shell Exploitation on Check Point Gateway”, and Check Point advisories sk1000302 and sk1000362, Nov 12, 2026. Schematic of the attack path described by Check Point, not a map of any victim’s network.
Graphic: Powered by Thorsten Meyer AI
Gateway Breaches Can Reach Servers
The incident shows why a compromised security gateway can create risks beyond the device itself. An attacker who gains a foothold on a gateway may use it to reach other systems on the network; in some reported cases, the intrusion extended to virtualization infrastructure, where a wiper could disrupt or destroy hosted data. Check Point’s account does not say that every compromised gateway led to a destructive attack.
For organizations running these appliances, the immediate issue is both patching and investigation. Applying the vendor’s fix addresses the known vulnerabilities, but it does not establish whether a device was previously compromised or remove every trace of an intrusion. Administrators need to review exposed gateways against Check Point’s indicators and consider connected systems where evidence points to further access. The reported incident count is Check Point’s account of observed cases, not a measure of all possible exposure.
Popular right now

Ninja CREAMi Scoop & Swirl 13-in-1 Ice Cream and Soft Serve Maker, NC701

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation

Breville BES870BSXL Barista Express Espresso Machine, Black Sesame
As an affiliate, we earn on qualifying purchases.
Two Flaws Enabled the Intrusion
PHP2Shell is the name used for two critical flaws in PHP, the programming language embedded in many websites and network appliances. The PHP project issued fixes on October 21 in versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12. CISA describes the vulnerabilities as allowing unauthenticated remote code execution. It added both PHP flaws to its exploited-vulnerabilities catalog on October 26.
Appliances may include PHP as part of their own software, so users generally need a device-maker update rather than a direct PHP package update. Check Point said its PHP2Shell hotfix for gateways was available October 23, before the observed attacks began. The later root-access flaw was distinct: Check Point disclosed CVE-2026-123039 and included its fix in the November Jumbo Hotfix on November 12. The attack chain therefore involved initial access followed by privilege escalation, not a single vulnerability.
““Only a couple of dozen unpatched systems, in a single region, were compromised in the observed incidents.””
— Check Point
Attribution and Full Scope Remain Open
Who carried out the attacks remains unconfirmed. The back door is associated with a malware family that ESET has linked to a China-nexus group, but the reported destructive activity and focus on Israeli organizations do not fit that group’s known interests. Check Point said its evidence does not support a high-confidence assessment of the operation’s nature.
The public account also leaves open whether additional organizations were affected outside the cases Check Point investigated, and whether every compromised gateway was identified. The supplied details describe the wiper’s behavior but do not establish the amount of data destroyed or the operational impact at each victim. Nor do they confirm that all second-wave targets were unaffected; Check Point reported no evidence of destructive activity in that wave.
Patch, Then Review Exposed Systems
Organizations using Check Point gateways should apply the November Jumbo Hotfix at the version-specific minimums in the vendor advisory, giving internet-facing Mobile Access portals priority. They should then review every exposed gateway for the compromise indicators Check Point lists and investigate relevant connected infrastructure, including ESXi hosts where appropriate. Older, unsupported versions require particular attention because the vendor says R81.10 and earlier are past end of support.
U.S. federal agencies face CISA’s November 16, 2026, action deadline for CVE-2026-123039. Further clarity may come from additional vendor, government or victim reporting, including information about the scope of the incidents and attribution. Until then, the confirmed account is limited to the cases Check Point investigated and the evidence it has publicly described.
Key Questions
What is PHP2Shell in this incident?
It refers to two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, that attackers used to execute code through Check Point Security Gateway Mobile Access portals.
Which Check Point fix should administrators install?
Check Point recommends its November Jumbo Hotfix for all Management Servers and Security Gateways. The minimum cited releases are Take 14 on R82.20, Take 52 on R82.10, Take 132 on R82 and Take 174 on R81.20; administrators should consult the vendor advisory for applicable systems.
Did every compromised gateway run a wiper?
No. Check Point reported wiper activity in some incidents in the first wave, which targeted Israeli organizations. It said it found no evidence of destructive activity in the November 2 wave across multiple countries.
Is the attacker’s identity known?
No. Check Point has not attributed the operation with confidence. A malware-family link reported by ESET does not establish who was responsible for these attacks.
What should organizations do after patching?
They should check exposed gateways for the indicators in Check Point’s advisory and investigate connected systems if the evidence suggests attackers moved beyond the gateway. Installing a patch does not by itself confirm whether a system was previously compromised.
Source: ThorstenMeyerAI.com
