Check Point gateways: a ‘local’ 7.8 was the root step between PHP2Shell and an ESXi wiper
Attackers used the PHP2Shell flaws to reach Check Point Mobile Access portals, then a world-writable root socket to own the gateway. The fixes shipped a week before the first wave. End-of-support releases are affected and have no fix.
Two scores, one chain
Check Point has confirmed that attackers compromised unpatched Security Gateways through their Mobile Access portals between 30 October and 4 November 2026 [2]. The chain used two published flaw sets. The more dangerous half of it carries a ‘local’ label and a 7.8 score [2][3].
The first stage was PHP2Shell, CVE-2026-109618 and CVE-2026-109619. Check Point rates these 9.2 and describes them as unauthenticated remote code execution through firewall web interfaces [2]. That gave the attacker code execution as the portal’s service account [1].
The second stage was CVE-2026-123039 in Gaia OS. A root process, dynamic_server, listens on a socket created world-writable and executes the command strings it receives as root, without authentication [3]. Check Point scores it 7.8 because it needs existing local code execution [3]. PHP2Shell supplied exactly that.
What the record shows
The dates are the uncomfortable part.
- 23 October: security fixes for Security Gateway and Management available [2][9].
- 30 October: first wave against Israeli organisations through Mobile Access portals, with some destructive activity [1][9].
- 2 November: second wave against organisations in several countries and sectors, with no destruction observed [1][9].
- 4 November: last observed exploitation [2][9].
- 12 November: Check Point publishes its advisory, its research and support article sk1000362 [1][2][3].
- 13 November: CISA adds CVE-2026-123039 to its Known Exploited Vulnerabilities catalog. The federal remediation deadline is 16 November [4][5][8].
Scale is stated differently in different Check Point documents. The support article says Check Point observed exploitation “against a couple of dozen customers” [3]. The advisory says a couple of dozen unpatched systems “in a single region” were compromised [2]. The research write-up gives no total and describes the second wave as hitting organisations worldwide [1]. Customers and systems are not the same unit, and a single region does not sit easily with a multi-country second wave. Readers should treat the count as approximate.
Affected versions also differ. The advisory lists R82.20, R82.10, R82 and R81.20 for CVE-2026-123039 [2]. The support article adds R81.10 and R81, and lists no fix for them because they are end of support [3]. The fixed Jumbo Hotfix takes are R82.20 Take 14, R82.10 Take 52, R82 Take 132 and R81.20 Take 174 [3][5].
After root
Check Point Research describes what followed [1]. The attackers placed PHP web shells in the portal’s template directory. They installed a persistent gateway implant it calls TSGA, with encrypted remote access, configuration theft, persistence across backups and snapshots, and tampering with binary firewall logs. A companion library, TSProxy, was injected into appliance processes to carry marked attacker connections [1].
In one case the intruder ran a network scanner from the gateway and moved over SSH to a VMware ESXi host using the vpxuser account [1][4]. There it ran a Linux wiper, destroy_v6, which deletes files of any extension and by default overwrites them with zeros first [1]. It left notes named DREAM_ANNEXATION.txt [1]. Check Point says the note makes no payment demand [2].
Attribution is open. Check Point Research assesses TSGA and TSProxy as modified variants of PhiliKit, a toolkit ESET previously associated with the China-nexus cluster UNC5221 [1][10]. It cites hosting and working-hours patterns that point the same way [1]. It then states that “the evidence does not allow us to assess with high confidence the true nature of this operation” [1]. It lists a single actor, an access broker, a false flag and a destructive smoke screen as possibilities [1]. This article takes no position beyond the researchers’.
What it means
PHP2Shell is not a Check Point bug. It is a flaw in PHP itself. GreyNoise had recorded 262,781 sessions against its sensors by 16 November, including 38,391 exploitation attempts and 1,265 confirmed successful exploitations [6]. Bitsight counts nearly 37 million internet-facing systems running PHP or PHP-related software, and says only updating PHP on the host closes the gap [7].
An appliance hides that PHP from its owner. The fix arrives as a vendor hotfix, on the vendor’s schedule, and must be installed by someone who may not know the gateway runs PHP at all. Here the vendor shipped in time. The window between fix and first wave was a week [2].
The second lesson is about scoring. CVE-2026-123039 alone needs a foothold [3]. Paired with a pre-authentication flaw on the same box, it turns a web worker into root on a security boundary. Prioritising by score alone would have put it behind the 9.2. In practice it decided whether the attacker could persist, hide traffic and pivot.
What to do
- Install the November Jumbo Hotfix on all gateways and management servers. Prioritise internet-facing Mobile Access deployments [2][3].
- Confirm the fix rather than the version. Check Point says the socket at /tmp/dynamic_socket should show mode 0660, owner root, group config, and that blocked calls are logged in /var/log/dynamicCli.log [3].
- If a box runs R81.10 or R81, plan the upgrade now. Until then, the documented workaround is to stop dynamic_server, at the cost of Dynamic CLI commands [3].
- Check every gateway that was exposed between 23 October and the date it was patched. Check Point Research lists host artefacts: session files containing upload_progress_pwn, bursts of PHP worker crashes, unexpected zz*.tpl templates, a process named slot_CPconfigdaemon, an unexpected /lib/libcpfwcommon.so and a listener on TCP 11072 [1].
- Look for gaps in firewall traffic logs. TSGA can tamper with them [1][5].
- Review SSH from gateways into virtualisation hosts, and vpxuser use in particular [1].
- Where indicators exist, treat patching as insufficient. One responder recommends rebuilding from clean media or a snapshot from before 30 October and rotating every credential the gateway held [8]. Check Point notes that the absence of known indicators does not prove a system is clean [5].
Security gateways are the most exposed systems many organisations own, and they run software their owners do not see. This campaign shows how a library flaw becomes a firewall compromise in seven days. Teams in APAC running Check Point should verify the socket permissions and their exposure window this week.
Sources
Every R3KONX article cites its primary material. 10 sources, in order of first citation. Links open the original publication.
- PHP2Shell exploitation on Check Point Gateway Check Point Research · 2026-11-12
- Security advisory: active exploitation of PHP2Shell and local privilege escalation Check Point · 2026-11-12
- sk1000362: CVE-2026-123039, local privilege escalation to root in the DynamicCLI process via local world-writable control socket Check Point Support Center · 2026-11-12
- Hackers exploit PHP2Shell flaws in Check Point gateways to deploy TSGA backdoor and wipe ESXi files The Hacker News · 2026-11-13
- Check Point flaw exploited as CISA's Nov. 16 deadline hits eSecurity Planet · 2026-11-17
- PHP2Shell (CVE-2026-109618 / CVE-2026-109619) exploitation tracker GreyNoise · 2026-11-16
- PHP2Shell exploitation hits government The Hacker News · 2026-10-25
- CVE-2026-123039 Check Point firewall root on CISA KEV: how to fix and check HOL · accessed 2026-11-18
- Check Point CVE-2026-123039 exploited with PHP2Shell OP Innovate · accessed 2026-11-18
- China-aligned groups ramp up attacks The Hacker News · 2026-06-01
Researched and written by the R3KONX Analysis Desk from the cited primary material. The technical account of the intrusions comes from Check Point and Check Point Research, the only parties with incident visibility. Counts of affected customers differ between Check Point documents and are reported as given. Attribution is reported as the researchers' assessment, which they state is unresolved. Corrections: event@r3konx.asia.
