What is Check Point Gaia?
Gaia is the hardened Linux-based operating system that runs on Check Point's security appliances: Quantum and Force firewalls, Security Gateways, Security Management Servers, Multi-Domain Security Management, Log Servers, and Maestro Orchestrator. Administrators drive it through Clish, a restricted command shell, and through the Gaia web portal; both sit on top of a configuration layer that ultimately executes as root.
An appliance running Gaia is a high-value target for the obvious reason that it is the device enforcing the network boundary. Root on a firewall means the rule base, the VPN certificates, the authentication secrets, and the logs are all under attacker control, and the log tampering means the record of what happened next is under their control too. It is also a pivot point with routed reachability into segments that nothing else can reach.
Overview
CVE-2026-123039 is a local privilege escalation to root in Gaia's DynamicCLI service. The dynamic_server daemon runs as root and listens on a local Unix domain socket, reported as /tmp/dynamic_socket, which on affected builds is created world-writable (mode 0777) and performs no authentication or identity check on connecting processes. Any local user who can write to that socket can submit a request and have the root daemon execute it.
Check Point's CNA entry scores the flaw 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and NVD records CWE-732 and CWE-862. NVD finished its analysis on 2026-11-14 and now carries the same CVSS 3.1 base score of 7.8 with that vector, rating the issue HIGH.
The 7.8 understates the operational impact because the flaw is not used on its own. Check Point observed it as the second stage of an intrusion chain: attackers first reached code execution on Mobile Access portals through the PHP2Shell flaws CVE-2026-109618 and CVE-2026-109619, which gave them the portal service account, then used CVE-2026-123039 to turn that account into root. Check Point says the flaw was exploited against "a couple of dozen customers."
Affected Versions
| Product | Vulnerable | Fixed |
|---|---|---|
| Gaia R82.20 | Earlier than Jumbo Hotfix Take 14 | Take 14 or later |
| Gaia R82.10 | Earlier than Jumbo Hotfix Take 52 | Take 52 or later |
| Gaia R82 | Earlier than Jumbo Hotfix Take 132 | Take 132 or later |
| Gaia R81.20 | Earlier than Jumbo Hotfix Take 174 | Take 174 or later |
| Gaia R81.10 and R81 | Affected | No fixed take published at time of writing; see sk1000362 |
| Spark Firewalls, Smart-1 Cloud | Not affected | Not applicable |
Affected deployments span Check Point Force Firewalls, Security Gateways, Management and Log Servers, Multi-Domain Security Management and Multi-Domain Log Server, Scalable Platforms, and Maestro Orchestrator. Sources differ on the oldest affected branch: Check Point's own advisory and the main press coverage list R81 as the floor, while at least one secondary summary extends the range back to R80.30. Treat sk1000362 as authoritative.
Technical Details
The weakness is CWE-732, incorrect permission assignment for a critical resource, compounded by CWE-862, missing authorization. In plain terms, a privileged service left its front door unlocked and then did not ask who walked in. Two separate controls had to be absent for this to work: the filesystem permissions on the socket should have restricted which accounts can connect, and the daemon should have verified the peer's credentials before acting on a request.
Exploitation is a single write to a Unix socket from an unprivileged local account. No memory corruption, no race, no timing dependency, nothing to bypass, and the payload is whatever command the attacker wants run as root. Attack complexity is as low as it gets. The one real constraint is the attacker must already have local code execution on the appliance, which is why the CVSS vector carries AV:L and PR:L. After patching, the socket should show mode 0660 rather than 0777, which makes verification straightforward.
Discovery
Check Point identified the flaw through its own incident response into the PHP2Shell intrusions rather than through a proactive audit or an external report. No individual researcher or outside organization is credited in the advisory, and Check Point Research published the campaign analysis that first described the chain. The company's advisory sk1000362 and the companion Gaia Portal input validation issue CVE-2026-107484 (sk1000291) were published together on 2026-11-12, with the Canadian Cyber Centre mirroring them the same day as AV26-1154.
Exploitation Context
The campaign ran in two waves. The first began on 2026-10-30, roughly a week after the PHP2Shell patch was available, and targeted Israeli organizations; some of those victims suffered destructive follow-on activity. A broader second wave on 2026-11-02 hit organizations across multiple countries and sectors and showed no destructive component, which Check Point characterizes as opportunistic.
The post-exploitation tooling is specific and worth hunting for. Attackers wrote PHP web shells as zz*.tpl files into the portal templates directory, keyed on the hardcoded string zz2026, with uploads staged at /tmp/.up.tpl and copied to challenge_render.tpl. They deployed the TSGA backdoor as /tmp/CPconfigdaemon, relaunching as slot_CPconfigdaemon for persistence, listening on TCP 11072 across all IPv4 interfaces and communicating over the Unix socket /tmp/.p_sock. TSGA embeds the TSProxy component, dropped as /lib/libcpfwcommon.so, which provides encrypted SOCKS-style proxying. TSGA can exfiltrate configurations and tamper with firewall logs. In destructive cases, the attackers ran the gogo scanner, moved to a VMware ESXi host over SSH using the vpxuser account, staged the destroy_v6 wiper, and left ransom-style notes named DREAM_ANNEXATION.txt. Early indicators included PHP session files under /opt/CPcvpn-R81.20/tmp/ containing the marker upload_progress_pwn, alongside hundreds of Apache and PHP worker segmentation faults. Published network indicators are 130.94.19[.]204 and 130.94.19[.]168.
Attribution is unresolved. TSGA and TSProxy are modified variants of the PhiliKit toolkit, which ESET previously linked to the China-nexus group UNC5221 (Armory Castle). Check Point explicitly declines to attribute with confidence, noting that the destructive activity, the Israel focus, and the Hebrew-language wiper note fit that profile poorly, and that an initial access broker, a false flag, or destruction used as a smokescreen are all plausible. CISA does not flag known ransomware use, though the wiper activity is functionally worse.
Remediation
- Install the fixed Jumbo Hotfix take for your branch: R82.20 Take 14, R82.10 Take 52, R82 Take 132, or R81.20 Take 174 or later. For R81.10 and R81, consult sk1000362 for current guidance.
- Patch the PHP2Shell flaws CVE-2026-109618 and CVE-2026-109619 on any Mobile Access portal in the same change. Fixing the privilege escalation alone leaves the initial access path open, and fixing initial access alone leaves root escalation available to the next bug.
- If you cannot patch immediately, stop the
dynamic_serverprocess and prevent it from restarting. This is Check Point's stated workaround and it breaks the Dynamic CLI commands listed in sk144112, so confirm you are not depending on them. - Verify the fix by checking the socket permissions after patching: the control socket should be mode 0660, not 0777.
- Hunt before you clean up. Review
/var/log/dynamicCli.log, where legitimate requests use a fixed Clish wrapper, so any request that does not is suspect. Search the portal templates directory forzz*.tplfiles and the stringzz2026, check for/tmp/CPconfigdaemon,slot_CPconfigdaemon,/lib/libcpfwcommon.so, and/tmp/.p_sock, look for a listener on TCP 11072, and search PHP session files forupload_progress_pwn. Check connection logs for 130.94.19[.]204 and 130.94.19[.]168. - Extend the investigation to adjacent VMware ESXi infrastructure and to SSH authentication for the
vpxuseraccount, since lateral movement to ESXi and deployment of thedestroy_v6wiper were part of the destructive wave. - Preserve appliance logs and forensic images before remediating, in line with CISA's Forensics Triage Requirements under BOD 26-04. TSGA can tamper with firewall logs, so treat on-box logs as potentially unreliable and corroborate against an external log collector.
- If compromise is confirmed, rotate everything the appliance held: administrator credentials, VPN and device certificates, pre-shared keys, RADIUS and LDAP service account passwords, and API keys. Root on the appliance means all of it was readable.
- Federal civilian agencies must remediate by 2026-11-16.
Key Details
| Property | Value |
|---|---|
| CVE ID | CVE-2026-123039 |
| Vendor / Product | Check Point - Multiple Products |
| NVD Published | 2026-11-12 |
| NVD Last Modified | 2026-11-14 |
| CVSS 3.1 Score | 7.8 |
| CVSS 3.1 Vector | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| Severity | HIGH |
| CWE | CWE-732 find similar ↗ |
| CISA KEV Added | 2026-11-13 |
| CISA KEV Deadline | 2026-11-16 |
| Known Ransomware Use | No |
CVSS 3.1 Breakdown
Required Action
Timeline
| Date | Event |
|---|---|
| 2026-10-21 | PHP patches the PHP2Shell flaws CVE-2026-109618 and CVE-2026-109619, later used for initial access |
| 2026-10-26 | CISA adds both PHP2Shell flaws to the KEV catalog |
| 2026-10-30 | First exploitation wave against Israeli organizations, including destructive ESXi activity |
| 2026-11-02 | Broader second wave across multiple countries and sectors, no destructive activity observed |
| 2026-11-12 | CVE published; Check Point publishes sk1000362 and the fixed Jumbo Hotfix takes |
| 2026-11-13 | Added to the CISA Known Exploited Vulnerabilities catalog |
| 2026-11-14 | NVD completes analysis and assigns a CVSS 3.1 base score of 7.8 (HIGH) |
| 2026-11-16 | CISA BOD 26-04 remediation deadline |