CVE-2026-123039 is a privilege escalation flaw in Check Point’s Gaia operating system that attackers are already exploiting. A command-line service runs as root and accepts commands without any checks over a local socket that every user can write to. Check Point fixed the flaw on 12 November 2026 in its November Jumbo Hotfix and reports attacks against “a couple of dozen” customers. The US agency CISA added CVE-2026-123039 to its Known Exploited Vulnerabilities catalog on 13 November. In the observed attacks, the flaw served as the second stage after PHP2Shell in the Mobile Access portal.
CVE-2026-123039: What the flaw is
According to Check Point article sk1000362, Gaia’s dynamic or extended CLI is served by a process called dynamic_server. It runs as root and listens on the local IPC socket /tmp/dynamic_socket. On affected systems, the socket is created with 0777 permissions, so any user can write to it. The service does not authenticate the connecting process and executes whatever command string it receives as root.
A single request to the socket is therefore enough to run arbitrary commands with full privileges. The attacker must already be able to run code on the appliance, for example through a service account. Check Point rates the flaw at CVSS 7.8 (vector AV:L/AC:L/PR:L). The “high” rather than “critical” rating reflects the local attack path only. In practice, the flaw becomes dangerous as soon as it is chained with a bug that provides initial access.
Affected products and versions
Check Point lists the following product groups as affected:
- Check Point Force Firewalls (Security Gateways)
- Management and Log Servers
- Multi-Domain Security Management and Multi-Domain Log Server
- Maestro Orchestrator
Affected Gaia versions are R82.20, R82.10, R82 and R81.20, plus R81 and R81.10, which are already end of support. Spark Firewalls and Smart-1 Cloud are not affected, according to the vendor. The related blog post lists only R81.20 through R82.20 in its summary table, while the support article also names the older branches.
Updates: These Jumbo Hotfix takes fix the flaw
The fix is included in the Jumbo Hotfix Accumulators starting from the following takes:
- R82.20 from Take 14
- R82.10 from Take 52
- R82 from Take 132
- R81.20 from Take 174
sk1000362 lists no fix for the end-of-support branches R81 and R81.10. Anyone still running them will need to upgrade to a supported branch. After the update, the service blocks and logs unauthenticated calls. Check Point says the socket itself shows whether the fix is in place: ls -l /tmp/dynamic_socket should show srw-rw---- owned by root and group config (0660), not srwxrwxrwx.
For teams that cannot patch right away, the support article describes a workaround: the dynamic_server process can be stopped with dbset and prevented from restarting. The Dynamic CLI commands listed in sk144112 will then stop working. This is a stopgap, not a replacement for the hotfix.
How the attack worked: PHP2Shell plus root
In its security advisory of 12 November, Check Point describes an attack chain. The attackers gained initial access through PHP2Shell (CVE-2026-109618, CVE-2026-109619) in the gateways’ Mobile Access portal. We covered that PHP flaw in PHP2Shell: Critical RCE Flaw Puts 70 Percent of Websites at Risk. Check Point had shipped a hotfix for it on 23 October, one week before the first attacks. The attackers then used CVE-2026-123039 to escalate from the portal’s service account to root.
The technical analysis by Check Point Research adds detail. The activity began on 30 October and, according to the vendor, remained active until 4 November. A first wave on 30 October targeted organizations in Israel and included destructive activity against some of them. A broader second wave on 2 November hit organizations across several countries and sectors, where the researchers found no evidence of destruction.
After escalating privileges, the attackers placed PHP webshells in the directory used to build the portal login pages and installed a persistent backdoor called TSGA with its networking component TSProxy. In at least one case they moved from the gateway to a VMware ESXi host over SSH, ran a wiper called destroy_v6 and left politically themed notes named DREAM_ANNEXATION.txt.
Check Point is cautious about attribution. The analysis says TSGA and TSProxy are modified variants of the PhiliKit malware framework, which ESET has linked to the China-nexus group UNC5221. The evidence, however, does not support a high-confidence attribution. The actor may also have acted only as an initial access broker or planted a false flag.
Checking for compromise: log file and indicators
The vulnerable service logs every command it receives to /var/log/dynamicCli.log. Legitimate calls use a fixed Clish wrapper that, among other things, sources .CPprofile.sh and sets set -o noglob. Check Point recommends three checks on every firewall and cluster member:
- Look for
Received =entries that do not contain this wrapper. - Look for use of the
system()sink (entries withReceived = #return_value#), which is rare or absent in normal traffic. - Look for commands typical of exploitation, such as
id,whoami, access to/etc/shadow,nc,/dev/tcp,curl,wget,base64,useraddorauthorized_keys.
After the update, entries reading “Rejected connection from unauthorized uid” indicate blocked attempts. An unexpected UID, such as 99 for nobody, points to a blocked escalation attempt, Check Point says, and should be correlated with portal and authentication logs.
Check Point also published further indicators from the investigated cases:
- scanning source addresses 130.94.19[.]204 and 130.94.19[.]168
- PHP session files containing the string
upload_progress_pwn - a process or binary named
CPconfigdaemonposing as a Check Point component - files with “scanner” or “wiper” in their names under
/tmpor/temp - a note referencing “Dream Annexation” with no payment demand
- unexplained gaps in firewall traffic logs, especially after a crash of the logging daemon
Check Point stresses that the absence of these traces does not rule out compromise.
Other fixes in the November Jumbo Hotfix
The cumulative hotfix addresses two more flaws that the vendor says are not being exploited. CVE-2026-107484 (CVSS 7.3, sk1000291) lets an authenticated user escalate privileges through Gaia Portal backend handlers and affects all versions from R80 to R82.20. CVE-2026-120490 (CVSS 3.8, sk1000364) concerns a privilege boundary between management and gateway via NAT rules in R81.20 and R82.
Assessment and priorities
CISA has given US federal agencies until 16 November and also requires a forensic triage. The Canadian Centre for Cyber Security tracks the case in advisory AV26-1154. The deadline does not apply to operators outside the US federal government, but the order of steps is clear:
- Update internet-facing gateways with Mobile Access first.
- Install the November Jumbo Hotfix on all management servers and gateways.
- Run the log checks on already patched systems too, since attacks started on 30 October.
- If anything matches, treat credentials and keys on the appliance as compromised and check adjacent systems such as hypervisors.
The case is part of a series of attacks on edge security appliances, most recently CVE-2026-116606 in Barracuda ESG. Citrix also fixed a large batch of NetScaler flaws this week, see our coverage of CVE-2026-120868. Anyone running such devices should not wait for the regular maintenance cycle to patch their gateways.




