skulldc

CISA lists Check Point Gaia DynamicCLI root socket flaw CVE-2026-123039 as exploited

A root-owned Gaia OS DynamicCLI daemon listens on a world-writable socket without authenticating callers, so an authenticated local user can run commands as root.

What CISA added

On 2026-11-13 CISA added CVE-2026-123039 to its catalog of known exploited vulnerabilities (KEV). The entry is titled “Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability”, with Check Point as the vendor and Multiple Products as the product. It maps to two weaknesses: CWE-732, incorrect permission assignment for a critical resource, and CWE-862, missing authorization. Known ransomware campaign use is listed as Unknown.

For US federal civilian agencies bound by BOD 22-01, the due date is 2026-11-16, three days after the listing.

The KEV description names the affected products: Check Point Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway, and Security Management Server.

How the flaw works

Both the KEV entry and the NVD record describe the same mechanism. The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket, which NVD gives as /tmp/dynamic_socket. The daemon does not authenticate the processes that connect to it.

That combination is the whole bug. Because the socket is world-writable, any local process can open it. Because the daemon does not check who is connecting, it accepts whatever arrives. Because it runs as root, the command it executes runs as root too. In the words of the record, an authenticated local user “can send a command to the socket and have it executed as root”.

The attacker therefore needs a local, authenticated foothold first. This is a privilege escalation from an ordinary local account to root, not a remote entry point on its own.

Severity

The NVD record was published on 2026-11-12 and is in the status Undergoing Analysis. It carries a secondary CVSS 3.1 base score of 7.8 HIGH supplied by Check Point, with the vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. That reads as a local attack vector, low complexity, low privileges required, no user interaction, unchanged scope, and high impact on confidentiality, integrity and availability. The local vector and low privileges match the description: a logged-in user who is not root.

What to do

The vendor reference is Check Point support article sk1000362, linked from both the KEV notes and the NVD references.

The KEV required action is to apply mitigations in accordance with vendor instructions, following CISA’s BOD 26-04 guidance on prioritizing security updates based on risk and its “Forensics Triage Requirements”. Where mitigations are unavailable, the guidance is to follow the applicable BOD 26-04 guidance for cloud services or discontinue use of the product. Stakeholders are also asked to evaluate each asset’s internet exposure.

Since the flaw turns any authenticated local account into root, the forensics part of the required action deserves attention alongside the fix: on an affected gateway or management server, every local account is a potential path to full control of the device.


Source: CVE-2026-123039 (NVD, CISA KEV)