Why Check Point Gateway Patches Matter In PHP2Shell Attacks
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: Why Check Point Gateway Patches Matter In PHP2Shell Attacks on ThorstenMeyerAI.com

Before you orderOffer from Amazon

Get the little things that make your day delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

Check Point says attackers used PHP2Shell flaws to enter unpatched Security Gateways between October 30 and November 4, then exploited a separate flaw to gain root access. The company’s November Jumbo Hotfix addresses the root-access flaw; CISA added it to its exploited-vulnerabilities catalog and gave U.S. federal agencies until November 16 to act. Check Point reported limited observed compromises, but some first-wave incidents involved a destructive wiper.

Check Point says attackers compromised unpatched Security Gateways from October 30 through November 4 by exploiting PHP2Shell flaws and then using a separate vulnerability to gain root access. The company’s November Jumbo Hotfix addresses that root-access flaw, while the U.S. Cybersecurity and Infrastructure Security Agency added it to its exploited-vulnerabilities catalog on November 13 and ordered federal agencies to act by November 16.

Check Point’s November 12 investigation says the attackers reached internet-exposed Mobile Access portals on gateways that had not received the PHP2Shell fix. The two PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, allowed code execution through the portal. Attackers then used CVE-2026-123039, a separate flaw in the Gaia operating system, to elevate their access to root, the device’s highest-privilege account.

The company said it observed “only a couple of dozen unpatched systems, in a single region” being compromised. In a first wave targeting Israeli organizations, some attackers moved from gateways to VMware ESXi servers and ran a wiper called destroy_v6, which overwrites files with zeros before deleting them. A second wave, beginning November 2 and targeting organizations in multiple countries, showed no evidence of destructive activity, according to Check Point.

Check Point says the PHP2Shell gateway fix was available on October 23, before the observed attacks began. The separate root-access flaw was disclosed and patched on November 12. The vendor recommends installing the November Jumbo Hotfix on all Management Servers and Security Gateways, prioritizing internet-facing Mobile Access portals, and checking exposed devices for signs of compromise.

At a glance
updateWhen: Investigation and hotfix published Nove…
The developmentCheck Point disclosed attacks on unpatched Security Gateways and released a hotfix addressing a root-access flaw that attackers used after gaining entry through PHP2Shell.

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

  1. Scanfrom Oct 30Unpatched gateways with an internet-facing Mobile Access portal are probed
  2. Way inPHP2Shell (CVE-2026-109618, CVE-2026-109619) runs code as the portal’s service account closed by fix
  3. RootCVE-2026-123039 in DynamicCLI turns that into full root rights closed by fix
  4. Back doorWeb shells in the portal’s login-page folder; TSGA back door with TSProxy hidden in appliance processes
  5. ReconThe gogo scanner maps internal systems from the gateway
  6. WipeSSH to a VMware ESXi host, destroy_v6 wiper, a note that rejects ransom talk (first wave, some victims)
The fix: November Jumbo Hotfix

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

A gateway sits between an organization’s network and outside connections, so a compromise can provide attackers with a foothold inside an environment. In these incidents, the sequence mattered: PHP2Shell provided initial code execution, while CVE-2026-123039 allowed attackers to turn that limited access into root privileges. A patch for the entry route alone would not address the later privilege-escalation flaw.

The reported wiper activity shows a possible consequence beyond access to the appliance itself. Check Point says some attackers reached VMware ESXi hosts and ran software designed to destroy data. It reported no evidence of destructive activity in the second wave, so the observed impact differed between incidents. The company’s account does not establish how many organizations suffered data loss or what systems beyond those it described were affected.

For administrators, the advisory calls for action across both Management Servers and Security Gateways, not just the systems known to have been compromised. CISA’s deadline applies to U.S. federal agencies; other organizations should use the vendor’s affected-version guidance and their own exposure assessments to set response priorities.

Products Worth Considering

Garmin Forerunner 970 GPS Running and Triathlon Smartwatch, 47mm, Carbon Gray DLC Titanium with Black/Whitestone Band

Garmin Forerunner 970 GPS Running and Triathlon Smartwatch, 47mm, Carbon Gray DLC Titanium with Black/Whitestone Band

As an affiliate, we earn on qualifying purchases.

How the Two-Flaw Chain Worked

PHP2Shell is the name used for two critical PHP vulnerabilities. PHP, a programming language used in web applications and embedded in some network appliances, fixed the flaws on October 21 in releases 8.2.35, 8.3.36, 8.4.27 and 8.5.12. CISA describes them as allowing unauthenticated remote code execution. It added both to its Known Exploited Vulnerabilities catalog on October 26.

Device software may include PHP without making that component’s version apparent to customers; appliance users generally depend on the device manufacturer to deliver an appropriate update. Check Point’s advisory said the PHP vulnerabilities could allow remote code execution through firewall web interfaces. The gateway hotfix for PHP2Shell was available October 23, but the later root-access issue required a separate fix.

Check Point says the second flaw, CVE-2026-123039, involved a Gaia helper service called DynamicCLI. The vendor describes it as running with root privileges and accepting commands through a local socket without checking the caller. It rated the flaw 7.8 out of 10, or high, and said exploitation requires code execution on the appliance first. Check Point’s report says attackers placed web shells and a back door after gaining root access.

““Only a couple of dozen unpatched systems, in a single region, were compromised in the observed incidents.””

— Check Point

Attribution and Impact Still Unsettled

Who carried out the attacks remains unknown. Check Point said its evidence does not support a high-confidence assessment of the operation. The back door belongs to a malware family that ESET has linked to a China-nexus group, according to the source material, but that association does not establish who conducted these incidents. Check Point also said the destructive, Israel-focused activity does not fit that group’s known interests.

The available account does not establish the full number of affected organizations, the amount of data destroyed, or whether attackers retained access beyond the cases described. Check Point reported no evidence of destructive activity in the second wave, but that finding is limited to the incidents it investigated. The broader effect on organizations and any further attack activity remain unclear.

Patch, Then Check Exposed Gateways

Organizations should install the November Jumbo Hotfix on their Management Servers and Security Gateways, giving internet-facing Mobile Access portals priority, and inspect exposed systems for the indicators listed in Check Point’s advisory. The source lists these minimum hotfix takes: Take 14 on R82.20, Take 52 on R82.10, Take 132 on R82, and Take 174 on R81.20. R81.10 and older versions are past end of support, according to the advisory summary.

U.S. federal agencies face CISA’s November 16 deadline for addressing CVE-2026-123039. Other organizations should follow the vendor’s patch guidance and determine whether their systems were exposed or show evidence of compromise. The next key developments are likely to be further incident findings, any additional attribution evidence, and updates from Check Point or CISA on the affected products and response guidance.

Key Questions

What did attackers exploit on Check Point gateways?

Check Point says attackers first used PHP2Shell, comprising CVE-2026-109618 and CVE-2026-109619, through Mobile Access portals. They then used CVE-2026-123039 to elevate their access to root.

Does the November Jumbo Hotfix address both parts of the attack?

Check Point says the November Jumbo Hotfix includes the fix for CVE-2026-123039, the root-access flaw. The vendor says the PHP2Shell gateway fix had already been available on October 23. Administrators should follow the vendor’s instructions to apply the specified hotfixes and verify their systems.

Were all compromised organizations hit by a wiper?

No. Check Point says some incidents in the first wave involved the destroy_v6 wiper on VMware ESXi hosts. The company reported no evidence of destructive activity in the second wave.

Who was responsible for the attacks?

Check Point has not attributed the attacks with high confidence. The reported link between the back door’s malware family and a China-nexus group does not establish that the group carried out these incidents.

What should organizations do now?

Install the November Jumbo Hotfix on Management Servers and Security Gateways, prioritize internet-facing Mobile Access portals, and check exposed devices for the compromise indicators in Check Point’s advisory. CISA set November 16 as the deadline for U.S. federal agencies to address CVE-2026-123039.

Source: ThorstenMeyerAI.com

You May Also Like

The Continual Learning Research Map: Where the Memento Constraint Stands in May 2026

An update on the research landscape of the Memento Constraint, highlighting current approaches, timelines, and remaining uncertainties in achieving continual learning in AI models.

The OAuth Permission Apocalypse.

Analysis of the ‘Allow All’ OAuth permission pattern, its risks, and implications for enterprise security in 2026.

PHP2Shell And AI: Revisiting A Security Story 22 Years In The Making

PHP released fixes for two critical remote-code-execution flaws found by researchers at Calif and Wiz, with AI tools assisting parts of the research.

A Skill Is a Folder, Not a Prompt: What Anthropic Learned Running Hundreds of Them

Anthropic reveals that their AI Skills are structured as folders containing instructions, scripts, and assets, transforming prompt engineering into durable organizational assets.