🔍 Read the full analysis: From PHP2Shell To Wiper: What Check Point Gateway Defenders Should Patch on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Check Point says attackers used PHP2Shell flaws and a separate root-access vulnerability to compromise a small number of unpatched Security Gateways from Oct. 30 to Nov. 4. Some intrusions included a wiper on VMware ESXi hosts; CISA added the root flaw to its exploited-vulnerabilities catalog and set a Nov. 16 deadline for U.S. federal agencies. Check Point advises installing its November Jumbo Hotfix and investigating exposed gateways.
Check Point says attackers compromised unpatched Security Gateways between Oct. 30 and Nov. 4 by exploiting PHP flaws and then using a separate vulnerability to gain root access. In some incidents, attackers moved from the gateways to VMware ESXi hosts and ran a data-wiping program; the findings prompted CISA to add the root flaw, CVE-2026-123039, to its exploited-vulnerabilities catalog on Nov. 13, with a Nov. 16 deadline for U.S. federal agencies.
Check Point’s Nov. 12 investigation says the attackers reached gateways through their Mobile Access portal, using two critical PHP vulnerabilities known as PHP2Shell: CVE-2026-109618 and CVE-2026-109619. Those flaws allowed remote code execution, according to CISA. The attackers then used CVE-2026-123039 to obtain root privileges on the appliance. Check Point rates that separate flaw 7.8 out of 10, or high, and says it requires an attacker to have code execution on the device first.
In a first wave targeting Israeli organizations, Check Point observed some attackers moving from gateways to VMware ESXi servers and launching a wiper called destroy_v6. The program overwrites files with zeros before deleting them. Its note, DREAM_ANNEXATION.txt, rejects ransom negotiations, according to Check Point. A second wave on Nov. 2 targeted organizations in multiple countries; Check Point said it found no evidence of destructive activity in those incidents.
Check Point says the observed incidents involved “only a couple of dozen unpatched systems, in a single region.” It advises customers to install its November Jumbo Hotfix on all Management Servers and Security Gateways, prioritizing internet-facing Mobile Access portals, then check exposed systems for signs of compromise. The listed minimum takes 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 past end of support.
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
Patch Exposure Before Intrusion
The incident shows how an internet-facing appliance can become an entry point into a wider company network. The PHP flaws provided a route to run code through the portal; the separate root flaw then let an intruder escalate privileges on the gateway. Check Point’s account describes a chain from web-facing access to administrator-level control, followed in some cases by movement to infrastructure hosting virtual machines.
For defenders, installing the hotfix is only part of the response. Check Point also recommends examining exposed gateways because a system may have been compromised before patching. The observed wiper activity makes this more than a software-update issue: organizations may need to assess whether other systems, including ESXi hosts, were reached and whether data was destroyed. The source does not say how many organizations suffered wiping or quantify the resulting damage.
CISA’s deadline adds a near-term requirement for U.S. federal agencies. Its catalog listing identifies CVE-2026-123039 as exploited and requires action by Nov. 16. The agency’s deadline does not establish that all affected gateways were compromised, but it underscores the need to check exposure and apply the vendor’s fix promptly.
Products Worth Considering

Samsung Odyssey G7 G75F 40-Inch WUHD Curved Gaming Monitor

Apple MacBook Air 15-inch Laptop with M5 Chip, 16GB Memory, 512GB SSD, Liquid Retina Display, and Touch ID (Midnight)

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite
As an affiliate, we earn on qualifying purchases.
Two Flaws, Two Fix Timelines
The PHP vulnerabilities and the gateway root flaw had different disclosure and patch timelines. The PHP project fixed PHP2Shell in releases published on Oct. 21, and CISA added the two PHP CVEs to its Known Exploited Vulnerabilities catalog on Oct. 26. Check Point says a gateway hotfix for PHP2Shell was available on Oct. 23, before the attacks it observed began on Oct. 30.
The root-access flaw was disclosed by Check Point on Nov. 12, when the company also issued its November Jumbo Hotfix. That distinction matters: the PHP flaws opened the way to code execution, while CVE-2026-123039 provided a route from that access to root. CISA warns that PHP may be embedded in other products, so its presence may not be obvious to operators. Check Point’s update is therefore specific to its appliances; administrators must follow the relevant vendor guidance rather than assume that updating PHP on a separate server patches a gateway.
Check Point says attackers placed web shells in the Mobile Access portal’s page-building directory and installed a back door called TSGA, designed to persist after a restart. The company’s report cites signs of exploitation on affected gateways, including unusual PHP session files and repeated crashes in portal web workers. These details support the company’s account of the intrusion, but they do not establish who was responsible.
“Only a couple of dozen unpatched systems, in a single region, were compromised in the observed incidents.”
— Check Point
Attribution and Damage Remain Unclear
Who carried out the attacks remains unknown. Check Point has not attributed them with confidence. The investigation says the back door belongs to a malware family ESET has linked to a China-nexus group, but Check Point notes that the destructive activity and focus on Israeli organizations do not fit that group’s known interests. That association is not proof that the group conducted this operation.
The company’s reported count covers a couple of dozen compromised, unpatched systems in one region. The available account does not establish the total number of organizations affected, whether other intrusions went undetected, or how much data was lost or made unrecoverable. Check Point reported no evidence of destructive activity in the second wave, but that finding is limited to the incidents it investigated. The source also does not specify how many ESXi hosts were affected or whether every gateway with signs of compromise was fully contained.
Apply the Hotfix and Investigate
Organizations using Check Point Security Gateways should compare their software versions with the vendor’s November Jumbo Hotfix guidance, install the applicable minimum take, and prioritize internet-facing Mobile Access portals. They should also review every gateway that was exposed for the signs of compromise listed in Check Point’s advisory; patching alone does not determine whether an intruder had already established persistence.
U.S. federal agencies are subject to CISA’s Nov. 16, 2026, action deadline for CVE-2026-123039. Check Point has not announced an attribution or a revised estimate of affected systems in the source material. Further reporting may clarify the scope of the intrusions, the extent of any ESXi damage, and whether the vendor or agencies identify additional indicators or affected versions.
Key Questions
Which vulnerability did CISA add to its exploited-vulnerabilities catalog?
CISA added CVE-2026-123039, the Check Point gateway root-access flaw, on Nov. 13, 2026. It set Nov. 16 as the deadline for U.S. federal agencies to act.
What is PHP2Shell in this incident?
PHP2Shell refers to two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Check Point says attackers used them through the gateways’ Mobile Access portal to run code before exploiting the separate root flaw.
What should Check Point gateway administrators do?
Install the applicable November Jumbo Hotfix on Management Servers and Security Gateways, prioritizing internet-facing Mobile Access portals. Then investigate exposed gateways for the compromise signs listed in Check Point’s advisory. The source lists minimum takes for R82.20, R82.10, R82 and R81.20.
Did every observed attack include a wiper?
No. Check Point reports wiper activity in some incidents in the first wave targeting Israeli organizations. It said it found no evidence of destructive activity in the second wave, which began on Nov. 2 and targeted organizations in multiple countries.
Has Check Point identified the attackers?
No. Check Point said the evidence did not allow it to assess the operation’s nature with high confidence. A link between the back-door malware family and a China-nexus group has been reported by ESET, but the source does not establish that group as responsible for these attacks.
Source: ThorstenMeyerAI.com
