🔍 Read the full analysis: Can Patching Check Point Gateways Help Limit Wiper Risk? 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 Oct. 30 to Nov. 4, using PHP flaws and a separate vulnerability to gain root access. Some intrusions led to a wiper attack on VMware ESXi servers; the company’s November Jumbo Hotfix addresses the root-access flaw, and CISA has ordered U.S. federal agencies to act by Nov. 16.
Check Point says attackers compromised unpatched Security Gateways from Oct. 30 through Nov. 4, used a second vulnerability to gain root access, and in some cases moved to VMware ESXi servers to run a wiper that destroys data. The company published its investigation and a fix on Nov. 12; the U.S. Cybersecurity and Infrastructure Security Agency added the root-access flaw to its exploited-vulnerabilities catalog the next day, setting Nov. 16 as the deadline for federal agencies to address it.
Check Point’s investigation describes a chain involving two critical PHP vulnerabilities, known as PHP2Shell and tracked as CVE-2026-109618 and CVE-2026-109619. Attackers reached the flaws through the gateways’ Mobile Access portal on devices that had not received the relevant fix. The flaws allowed remote code execution, initially giving attackers access as the portal’s service account, according to the company.
Attackers then used CVE-2026-123039, a separate flaw in the Gaia operating system, to elevate their access to root. Check Point says root access enabled them to install web shells and a back door designed to persist across a restart. The company rated the root flaw 7.8 out of 10, or high severity, and said it requires an attacker to have already gained local code execution on the appliance.
In incidents targeting Israeli organizations, attackers sometimes moved from a gateway to a VMware ESXi host and ran a wiper called destroy_v6. Check Point says the program overwrites files with zeros and deletes them. A second wave on Nov. 2 targeted organizations in multiple countries, but the company reported no evidence of destructive activity in those cases. It said only a couple of dozen unpatched systems in one region were compromised in the incidents it observed.
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
Why Gateway Patches Matter
The incidents show how a vulnerability in an internet-accessible network appliance can provide a route into systems behind it. Here, Check Point says the initial PHP flaws gave attackers a foothold on the gateway, while the separate root flaw allowed them to take control of the appliance. In some cases, the intrusion then reached ESXi infrastructure, where the reported wiper could disrupt or destroy data.
Patching can reduce the risk of this particular chain, but it cannot establish that a previously exposed gateway is clean. Administrators should treat updating and checking for signs of compromise as separate steps: install the vendor’s fix, then review exposed devices against Check Point’s indicators. The reported attacks were limited in number, according to the company, but their use of a wiper makes the potential consequence for affected organizations more severe than a simple device compromise.
The CISA deadline also gives the report an immediate operational consequence for federal agencies. Other organizations are not covered by that federal deadline, but internet-facing Mobile Access portals are among the systems Check Point says administrators should prioritize.
Popular right now

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation

Sony WH-1000XM6 Wireless Noise-Canceling Headphones, Black

De’Longhi Rivelia Fully Automatic Espresso Machine with Grinder and Milk Frother, Beige
As an affiliate, we earn on qualifying purchases.
Two Flaws, Separate Fix Timelines
The PHP project fixed the PHP2Shell vulnerabilities on Oct. 21 in supported PHP releases. Check Point says its hotfix for the PHP flaws on its gateways was available on Oct. 23, a week before the attacks it investigated began. That timing is distinct from the root-access flaw: Check Point says it disclosed CVE-2026-123039 and included its fix in the Nov. 12 Jumbo Hotfix.
The difference matters because fixing the initial entry point did not address the separate method used to gain root access. CISA added the PHP flaws to its Known Exploited Vulnerabilities catalog on Oct. 26, then added the root flaw on Nov. 13. CISA has directed federal agencies to remediate the root flaw by Nov. 16.
Check Point recommends installing the November Jumbo Hotfix on Management Servers and Security Gateways, prioritizing internet-facing Mobile Access portals. Its listed minimum releases include Take 14 on R82.20, Take 52 on R82.10, Take 132 on R82 and Take 174 on R81.20. The company says R81.10 and older versions are beyond end of support.
“Only a couple of dozen unpatched systems, in a single region, were compromised in the observed incidents.”
— Check Point
Attribution and Exposure Remain Open
Who carried out the attacks is not established. Check Point said its evidence did not support a high-confidence assessment of the operation’s true nature. The back door is associated with a malware family that ESET has linked to a China-nexus group, but the destructive activity and focus on Israeli targets do not fit that group’s known interests, according to the source report. That mismatch is a reason for caution, not proof of who was responsible.
The company’s findings also describe incidents it observed, not necessarily the full extent of exploitation. The available account does not establish whether other gateways were compromised, whether all back doors or web shells have been found, or whether additional organizations suffered destructive activity. Check Point’s estimate of a couple of dozen systems applies to the observed incidents and should not be treated as a count of every potentially exposed device.
It is also not clear from the supplied reporting whether all affected organizations have completed patching and forensic checks, or whether attackers retained access elsewhere in victim networks. A hotfix addresses the vulnerability; it does not by itself confirm that an already compromised system has been fully remediated.
Patch, Then Check for Intrusions
Administrators should install the November Jumbo Hotfix across affected Check Point Management Servers and Security Gateways, giving internet-facing Mobile Access portals priority. They should verify that devices are on the applicable fixed release and review each gateway that was exposed for the indicators listed in Check Point’s investigation. Systems running R81.10 or older are beyond support, so operators should consult Check Point’s guidance on supported versions and replacement or upgrade options.
U.S. federal agencies face the immediate Nov. 16 CISA deadline for CVE-2026-123039. Organizations outside that requirement should still use the advisory and investigation to guide their response. If a gateway shows signs of compromise, patching alone may not be enough; security teams will need to assess persistence and check connected infrastructure, including ESXi hosts, for evidence of the wiper or other attacker activity.
Further clarity will depend on incident investigations, additional victim reporting and any new technical findings from Check Point or other researchers. Until then, the company’s account supports treating the vulnerability chain as an observed risk while keeping attribution and the full scope of impact unresolved.
Key Questions
What did attackers do to Check Point gateways?
Check Point says attackers used PHP2Shell flaws through the Mobile Access portal, then exploited CVE-2026-123039 to gain root access. They installed web shells and a back door, and in some cases moved to an ESXi host to run a wiper.
Does the November hotfix address the vulnerabilities?
Check Point says its November Jumbo Hotfix includes the fix for the root-access flaw, CVE-2026-123039. The company says a hotfix for PHP2Shell on its gateways had been available since Oct. 23. Administrators should follow Check Point’s release-specific instructions and confirm the applicable fix is installed.
Does patching prove a gateway was not compromised?
No. Patching addresses the vulnerability but does not establish whether an attacker already gained access or left a back door. Check Point advises checking exposed gateways for the indicators of compromise in its investigation.
Who is believed to be behind the attacks?
Attribution remains uncertain. Check Point said it could not assess the operation with high confidence. A malware-family link reported by ESET does not, by itself, establish that the group associated with the malware carried out these attacks.
What is the deadline for U.S. federal agencies?
CISA set Nov. 16, 2026, for federal agencies to address CVE-2026-123039 after adding it to its exploited-vulnerabilities catalog on Nov. 13.
Source: ThorstenMeyerAI.com
