1. Executive summary
CVE-2026-123039 is a high-severity (CVSS 7.8) local privilege escalation in Check Point Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway and Security Management Server. The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket without authenticating connecting processes, so an authenticated local user can send a command to the socket and have it executed as root. CISA added the CVE to its Known Exploited Vulnerabilities catalog on 2026-11-13, which means exploitation has been observed in the wild, and set a remediation due date of 2026-11-16. For EMEA financial services the exposure is concentrated in perimeter and management-plane estate: a foothold on any Check Point host that reaches the socket converts to root on the device that enforces the network boundary or holds the security policy. The three-day federal deadline leaves little room; treat this as a P1 patch for any Check Point estate reachable by non-administrative local users.
2. Regulatory framing
| Article | Trigger (the fact in this item) | Practical impact |
|---|---|---|
| DORA Art. 17 | CISA records CVE-2026-123039 as exploited in the wild (KEV added 2026-11-13) against a security control product (firewall, security gateway, management server) in the ICT estate | The ICT-related incident management process must cover detection and response for compromise of the Check Point management and perimeter estate, not just the patching ticket |
| DORA Art. 18 | Exploitation of a boundary and policy-management device can affect the availability and integrity of the services it protects | Classification of the incident must account for the security-control role of the affected asset, not only the host itself |
| NIS2 Art. 21(2)(d) | The vulnerable product is a security gateway and management server that sits in the supply chain between the entity and its network | Supply chain security measures must extend to verifying and remediating the security products the entity depends on |
3. Technical analysis & attack chain
The flaw is an incorrect permission assignment for a critical resource (CWE-732) combined with missing authorization (CWE-862). The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket. It does not authenticate the processes that connect to it. Any authenticated local user who can reach that socket can send a command and have it executed with root privileges.
Confirmed steps, as described in the CVE record:
- An attacker obtains an authenticated local user session on a Check Point host running Gaia OS (Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway, or Security Management Server).
- The attacker connects to the DynamicCLI daemon's world-writable local socket.
- The daemon, running as root, accepts the connection without authenticating the connecting process.
- The attacker sends a command to the socket; the daemon executes it as root.
The record does not state the initial access vector that gets an attacker to a local user session, the socket path, the exact command syntax, or whether the flaw requires any particular Gaia OS version. It also does not name affected or fixed product versions. No fixed release is named in public reporting; the CISA entry directs defenders to apply mitigations in accordance with vendor instructions. The CVE record does not state which Check Point release closes the issue.
The impact is privilege escalation to root on a device that enforces network policy or holds security management data. On a Security Gateway or Firewall, root yields control of the traffic path. On a Security Management Server or Multi-Domain Security Management Server, root yields control of policy, logs and managed-gateway credentials. The CVE record does not describe post-exploitation behaviour, persistence, command-and-control, lateral movement or data access, and none should be inferred from the record alone.
CISA lists known ransomware campaign use as Unknown. No actor, campaign or attribution is named in the CVE record or in CISA's KEV entry, and no MITRE ATT&CK profile is associated with this item.
The related Check Point CVEs in the source set describe separate vulnerabilities and are not part of this event: CVE-2026-93616 (path traversal, unauthenticated script upload and execution on management and log servers), CVE-2026-85102 (improper certificate validation in Site to Site or Remote Access VPN, unauthenticated remote code execution on the gateway) and CVE-2026-50751 (IKEv1 authentication bypass allowing a VPN connection without a valid password). They are noted only so that a Check Point patch cycle is not mistaken for coverage of CVE-2026-123039; each has its own KEV entry and due date.
4. Mitigation & containment
P1 (within 24 hours)
- Apply the vendor mitigation for CVE-2026-123039 to every Check Point Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway and Security Management Server in the estate, following Check Point's instructions. No fixed release identifier is named in public reporting, so confirm the applicable fix with Check Point before closing the ticket.
- Treat the CISA due date of 2026-11-16 as the outer bound for internet-exposed and management-plane devices.
- Restrict local login on Check Point hosts to named administrators. The flaw requires an authenticated local user, so removing standing local accounts and shared logins on these devices removes the precondition for exploitation.
- Hunt for unexpected local logins and for processes spawned as root from the DynamicCLI daemon on Check Point hosts. The CVE record does not give the socket path or process names, so build the hunt from the device's own baseline rather than a published indicator.
P2 (within 72 hours)
- Review which accounts hold local shell access on Check Point management and gateway hosts and remove any that are not required for administration.
- Where a device cannot be patched inside the P1 window, isolate its management interface to a dedicated administrative network and remove general-purpose user access to the host.
P3 (within 7 days)
- Reconcile the Check Point inventory against the CISA KEV entries for the related Check Point CVEs (CVE-2026-93616, CVE-2026-85102, CVE-2026-50751) so that the patch cycle covers each with its own due date rather than assuming one fix closes all four.
- Record the remediation evidence against DORA Art. 17 incident-management and NIS2 Art. 21(2)(d) supply chain records.
5. Indicators of compromise
No indicators of compromise available in the source material. The CVE record describes the mechanism (a world-writable local socket on the Gaia OS DynamicCLI daemon that does not authenticate connecting processes) but gives no socket path, file hash, command string or network indicator.
6. Detection
Insufficient indicators to author detection rules. The CVE record gives no distinctive strings, command-line flags, file paths, socket paths, registry keys or filenames to anchor a YARA or Sigma rule, and constructing one from the prose description of the mechanism would not match the artefact.
CVE assessment
1 referenced CVE — 1 actively exploited (CISA KEV)
| CVE | CVSS | Exploited | EPSS | Summary |
|---|---|---|---|---|
| CVE-2026-123039 | 7.8 High | ⚠ KEV 2026-11-13 | 1% | The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket (/tmp/dynamic_socket) without authentic… |
7. Sources
- NVD, CVE-2026-123039 detail, https://nvd.nist.gov/vuln/detail/CVE-2026-123039, published 2026-11-13
- CISA Known Exploited Vulnerabilities, CVE-2026-123039 (Check Point Multiple Products), https://nvd.nist.gov/vuln/detail/CVE-2026-123039, KEV added 2026-11-13
- CISA Known Exploited Vulnerabilities, CVE-2026-93616 (Check Point Multiple Products path traversal), https://nvd.nist.gov/vuln/detail/CVE-2026-93616
- CISA Known Exploited Vulnerabilities, CVE-2026-85102 (Check Point Multiple Products improper certificate validation), https://nvd.nist.gov/vuln/detail/CVE-2026-85102
- CISA Known Exploited Vulnerabilities, CVE-2026-50751 (Check Point Security Gateway improper authentication), https://nvd.nist.gov/vuln/detail/CVE-2026-50751
8. Adverse Trace position
Adverse Trace assesses CVE-2026-123039 as high severity (CVSS 7.8) and confirmed exploited in the wild by its presence in CISA KEV, with a federal remediation due date of 2026-11-16. The client impact for EMEA financial services is elevated where Check Point gateways and management servers are in scope, because root on those devices yields control of the network boundary or the security policy; it is lower where Check Point is absent or the affected hosts are not reachable by non-administrative local users. No actor is attributed and no ransomware use is recorded. The mechanism is single-sourced to the CVE record and CISA KEV entry, and no fixed release identifier is published, so verify the vendor fix with Check Point before closing remediation. Adverse Trace will track Check Point's advisory for a fixed release and update this note when one is named. Clients should confirm their Check Point inventory and patch status against the 2026-11-16 deadline and report back.
Published via PulseTrace — Adverse Trace threat intelligence.