
Check Point has released emergency hotfixes for CVE-2026-123039, a local privilege-escalation flaw in Gaia OS that attackers have been using to get root on its gateways. BleepingComputer reports the exploitation has been going on since late October, and Check Point’s advisory says it “observed an active exploit of this vulnerability against a couple of dozen customers.” The flaw is in the DynamicCLI service: according to the advisory, the daemon runs as root and listens on a world-writable local socket (/tmp/dynamic_socket) without authenticating whoever connects, so an authenticated local user can send a command and have it run as root. The Hacker News gives it a CVSS score of 7.8 and notes it needs an attacker who already has local code execution on the appliance.
That is where PHP2Shell came in. In a separate report published November 12, Check Point Research describes attackers who first got into the Mobile Access portal using exploitation consistent with the PHP2Shell flaws (CVE-2026-109618 and CVE-2026-109619), then used CVE-2026-123039 to reach root. Check Point says this began on October 30 against Israeli organizations, roughly a week after a security fix became available, and that a broader second wave on November 2 hit organizations in several countries and sectors with no evidence of destructive activity. After gaining root, the attackers dropped PHP web shells, installed a backdoor called TSGA with an embedded networking component called TSProxy, scanned the internal network, and moved over SSH to a VMware ESXi host, where they ran a wiper called destroy_v6 and left politically themed DREAM_ANNEXATION.txt notes.
Check Point says TSGA and TSProxy are modified variants of PhiliKit, a toolkit earlier seen in attacks on Ivanti appliances and tied by ESET to a China-nexus group. It also says the evidence, including the wiper, the focus on Israel and the Hebrew-language note, does not support a high-confidence attribution; it lists several scenarios, including a false-flag operation. For background on the PHP flaws, see our earlier posts on the emergency PHP patch and the first confirmed working PHP2Shell exploitation.
How to check if you’re affected
Affected products and versions, as listed by The Hacker News from Check Point’s advisory, are versions R82.20, R82.10, R82, R81.20, R81.10 and R81 of Check Point firewalls, Management and Log Servers, Multi-Domain Security Management and Multi-Domain Log Server, and Maestro Orchestrator. BleepingComputer’s list names the Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway and Security Management Server. The advisory page (sk1000362) did not render for us, so we could not read the hotfix table: take the hotfix for your exact version from that advisory.
- Temporary mitigation. If you cannot install the hotfix yet, BleepingComputer says Check Point advises stopping the
dynamic_serverprocess and preventing it from restarting. - Look for exploitation. Check Point says evidence shows up as commands commonly associated with exploitation attempts, use of the
system()sink (uncommon or absent in legitimate traffic), and commands that do not go through the default Clish wrapper, which would indicate they ran as root through the socket. Check Point published indicators of compromise with its advisory. - Look for the PHP2Shell stage. In the intrusion Check Point investigated, session files containing an
upload_progress_pwnmarker appeared under/opt/CPcvpn-R81.20/tmp/, the portal’s Apache/PHP workers logged hundreds of segmentation faults, and web shells namedzz*.tplwere placed in the Mobile Access portal’s templates directory. - Look for the backdoor. Indicators in the report include
/tmp/CPconfigdaemonandslot_CPconfigdaemon(TSGA),/lib/libcpfwcommon.so(TSProxy), TCP port 11072, the Unix socket/tmp/.p_sock, and the source addresses 130.94.19[.]204 and 130.94.19[.]168. The full file hashes are in Check Point Research’s report. - Check the ESXi hosts behind the gateway. The attackers used the
vpxuserservice account over SSH from the gateway, so reviewing SSH logins to ESXi hosts from gateway addresses is a sensible check (our suggestion, not a step the sources state). Treating a gateway with these indicators as fully compromised and rebuilding it is also our own suggestion.
BleepingComputer also notes that in September Check Point warned of zero-day exploitation of two other flaws, CVE-2026-93616 (Security Management Server) and CVE-2026-85102 (Security Gateway); those are separate CVEs from this one.
Sources
- Check Point Research: PHP2Shell Exploitation on Check Point Gateway
- Check Point advisory sk1000362 for CVE-2026-123039 (page did not render; linked from BleepingComputer and The Hacker News)
- BleepingComputer: Check Point warns of zero-day flaw exploited for root access
- The Hacker News: Hackers Exploit PHP2Shell Flaws in Check Point Gateways to Deploy TSGA Backdoor and Wipe ESXi Files
- NVD: CVE-2026-123039
