Security / News explained
Check Point’s DynamicCLI flaw turns local access into root
Check Point’s November 12 hotfix releases address CVE-2026-123039. The flaw has been exploited after initial access, making patching and investigation separate pieces of the response.
Check Point has fixed CVE-2026-123039, a Gaia OS DynamicCLI vulnerability that allows an authenticated local user to execute commands as root. CISA added it to the Known Exploited Vulnerabilities catalog on November 13, 2026. The local-access requirement matters, especially because Check Point has documented attackers reaching this flaw after obtaining an initial foothold. [2] [3] [4]
Four Jumbo Hotfix release notes dated November 12 explicitly list the fix: R82.20 Take 14, R82.10 Take 52, R82 Take 132 and R81.20 Take 174. Those release-specific identifiers are more useful than a general statement that an appliance received a recent update. A release family and its installed hotfix need to be read together. [5] [6] [7] [8]
A privileged helper accepted the wrong callers
According to the vendor-authored CVE record, the DynamicCLI daemon runs as root and listens on a local socket at /tmp/dynamic_socket. Affected installations make that socket writable by everyone, while the service fails to authenticate the connecting process. A local user can therefore ask a privileged process to execute a command with root permissions. [2]
In plain terms, a helper with broad powers failed to establish who was asking for help. The socket being local reduces who can reach it directly, but a foothold inside the appliance can put an attacker on the other side of that boundary. Our interpretation is that local services belong in the security model alongside externally reachable ones.
Consider a hypothetical appliance where a web-facing process runs with restricted permissions. An unrelated flaw gives an attacker control of that process. Keeping the process restricted can limit the damage, provided that nearby privileged services enforce their own access checks. A permissive local command channel can defeat that separation. This example illustrates the boundary; it is not a claim about an additional incident.
Affected releases and the fixed hotfixes
The CVE record identifies Quantum Security Gateway and Quantum Security Management installations running R82.10 with Jumbo Hotfix Take 50 or below, R82.20 Take 10 or below, R82 Take 130 or below, and R81.20 Take 173 or below. These are the recorded affected ranges. The fixed Takes above come from the vendor’s published releases, rather than arithmetic applied to those ranges. [2]
The support advisory also lists older R81 and R81.10 releases, marked end of support, among affected versions. It identifies Check Point Spark Firewalls and Smart-1 Cloud as unaffected by this particular vulnerability. Owners of older deployments should use the current vendor guidance to establish a supported path. [1]
The advisory describes stopping DynamicCLI and preventing its restart as a mitigation, with a functional cost: Dynamic CLI commands become unavailable. That tradeoff needs an operator who understands the appliance’s dependencies. The permanent fixes enforce caller authorization and log rejected unauthenticated requests. [1]
For our readers, the useful management question is whether each gateway, management server and relevant cluster member has a confirmed disposition. A successful change on a visible gateway cannot establish the condition of a less visible management node. Record the actual release and hotfix, the selected remediation and any remaining operational dependency before closing the work.
Patching and investigating answer different questions
Check Point Research’s November 12 report describes exploitation beginning on October 30. In the investigated intrusion, PHP2Shell supplied initial access, followed by DynamicCLI privilege escalation. The report describes subsequent persistence and movement to a VMware ESXi host, including destructive activity. It also describes a broader November 2 wave without evidence of destruction. These are the researchers’ observations, with different outcomes across the reported activity. [4]
That sequence gives the local vulnerability practical context. It also explains why resolving the entry point and resolving the escalation path are separate tasks. Our assessment is that an incident review should consider the sequence an attacker could have traversed, while keeping every conclusion tied to retained evidence. A fixed appliance and an investigated appliance answer different questions.
The support article points investigators to /var/log/dynamicCli.log and describes suspicious command patterns. For fixed systems, it expects the socket’s owner and permissions to be root:config and 0660, and provides a log message for rejected unauthorized callers. Those checks help distinguish current protection from signs that deserve investigation; they do not make a single clean log a complete forensic assessment. [1]
Operationally, we would separate the record into the remediation completed now and the exposure investigated over time. Preserve relevant evidence through the organization’s response process, then assess the period during which an affected system was reachable through its actual access paths. Missing evidence remains an uncertainty to document, rather than a reassuring result.
The lesson is practical: a security appliance contains software boundaries of its own. Its management processes, local helpers and web services need explicit authorization between them. For this flaw, the immediate priorities are the vendor’s verified fixed release for the installed branch and an evidence-based review of possible earlier exploitation.
Sources + further reading
Source dates describe the original material. Publication above is the date this Zyel article went live.
- CVE-2026-123039: DynamicCLI local privilege escalation, sk1000362Check Point · Checked Nov 14, 2026
- Check Point-authored CVE-2026-123039 recordCVE Program / Check Point · Checked Nov 14, 2026
- Known Exploited Vulnerabilities catalog, November 13 snapshotCISA · Checked Nov 14, 2026
- PHP2Shell Exploitation on Check Point Gateway, November 12, 2026Check Point Research · Checked Nov 14, 2026
- R82.20 Jumbo Hotfix Take 14 release notesCheck Point · Checked Nov 14, 2026
- R82.10 Jumbo Hotfix Take 52 release notesCheck Point · Checked Nov 14, 2026
- R82 Jumbo Hotfix Take 132 release notesCheck Point · Checked Nov 14, 2026
- R81.20 Jumbo Hotfix Take 174 release notesCheck Point · Checked Nov 14, 2026
Reader discussion
What would you ask next?
Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.
No reader comments yet.