Advisory

CVE-2026-123039: Check Point Gaia OS DynamicCLI Local Privilege Escalation (HIGH, CVSS 7.8)

A world-writable, unauthenticated local socket in Check Point's Gaia OS DynamicCLI daemon allows any authenticated local user to execute arbitrary commands as root. This privilege-escalation flaw is confirmed actively exploited and is listed in the CISA Known Exploited Vulnerabilities catalog.

TL;DR: Apply Check Point's vendor-supplied patches or mitigations immediately across all affected Gaia OS–based products. CISA has added this vulnerability to the KEV catalog and mandates remediation under BOD 26-04.

What Is the Flaw?

CVE-2026-123039 is an incorrect permission assignment for a critical resource vulnerability (CWE-732) combined with a missing authentication for a critical function weakness (CWE-862). It carries a CVSS 3.1 score of 7.8 (HIGH) with the vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

The root cause is straightforward: the Gaia OS DynamicCLI daemon runs with full root privileges and listens on a local Unix domain socket located at /tmp/dynamic_socket. That socket is world-writable and performs no authentication of connecting processes. Because any locally authenticated user can open the socket and send commands, those commands are subsequently executed with root-level authority — granting the attacker complete control over the host.

  • Attack Vector: Local — a valid operating system account on the affected appliance or server is required.
  • Attack Complexity: Low — no special conditions or race conditions must be met.
  • Privileges Required: Low — any standard authenticated user is sufficient.
  • User Interaction: None — no administrator action is needed to trigger the flaw.
  • Impact: High across Confidentiality, Integrity, and Availability.

Affected Products

According to Check Point and CISA, the following product families running Gaia OS are affected:

  • Check Point Firewall
  • Check Point Multi-Domain Security Management Server
  • Check Point Scalable Platforms
  • Check Point Security Gateway
  • Check Point Security Management Server

Specific version ranges and hotfix identifiers are defined in the vendor's own advisory. Consult the Check Point Security Advisory directly for the authoritative list of affected builds and confirmed fixed versions.

Impact and Exploitation Status

CISA added CVE-2026-123039 to the Known Exploited Vulnerabilities (KEV) catalog on 2026-11-13, one day after NVD publication. CISA's addition indicates that this vulnerability has been exploited in the wild. Organizations should treat this as an active threat, not a theoretical risk.

Successful exploitation grants an attacker complete root access to the affected system. On Check Point security infrastructure, this means an adversary could:

  • Read, alter, or destroy firewall policy configuration and logs.
  • Extract sensitive cryptographic material, certificates, or VPN credentials stored on the appliance.
  • Modify routing or access-control rules, effectively eliminating network segmentation.
  • Pivot laterally to management servers overseeing an entire estate of gateways.
  • Disrupt availability of gateway or management services.

Because Check Point gateways and management servers sit at the perimeter and center of enterprise networks, privilege escalation on these devices carries disproportionately high organizational risk compared with similar vulnerabilities on general-purpose hosts.

Note: No EPSS score was available for this CVE as of 2026-11-14.

What to Do Now

CISA's required action under BOD 26-04 is to apply mitigations in accordance with vendor instructions. If no mitigation is available, discontinue use of the affected product. The following prioritized steps are recommended:

  1. Inventory immediately. Identify every Check Point appliance, gateway, management server, and scalable platform in your environment that runs Gaia OS.
  2. Consult the Check Point Security Advisory. Obtain the confirmed fixed version or hotfix from Check Point's official support portal and apply it without delay, following BOD 26-04 patching timelines.
  3. Restrict local access. While patching is underway, enforce the principle of least privilege on Gaia OS accounts. Remove or disable any non-essential local user accounts. Limit interactive shell access through SSH ACLs or jump-host controls.
  4. Review privileged-access paths. Audit which users, service accounts, or automation processes hold local login rights on Check Point appliances. Revoke access that is not operationally required.
  5. Enable logging and alerting. Ensure command-execution and daemon-connection events on Gaia OS are captured and forwarded to a SIEM. Look for unexpected socket activity under /tmp/.
  6. Cloud and internet-exposed assets. Per BOD 26-04 guidance, evaluate each asset's internet exposure separately and apply the appropriate patching deadline. For cloud-managed deployments, follow any cloud-specific guidance issued by Check Point or CISA.
  7. Document and report. Federal civilian agencies must adhere to BOD 26-04 reporting requirements. Private-sector organizations should follow internal vulnerability-management SLAs consistent with HIGH/actively-exploited severity.

Primary references: CISA KEV Catalog | NVD – CVE-2026-123039 | Check Point Security Advisory (vendor portal).

How External Security Testing Surfaces Exposure

Because this is a local privilege-escalation vulnerability (CVSS Attack Vector: Local), it is not directly reachable from the internet and will not appear as an open port on a standard network scan. However, external and internal security testing can still identify the conditions that make exploitation possible:

  • Authenticated configuration audits: A credentialed assessment of Gaia OS can confirm whether the DynamicCLI daemon is running, whether /tmp/dynamic_socket exists with world-writable permissions, and whether the patched version has been applied.
  • Patch and version verification: Comparing installed Gaia OS build numbers against the vendor's fixed-version matrix reveals unpatched assets that carry the vulnerability, even before any active exploitation occurs.
  • Privilege-access mapping: An internal assessment can enumerate local user accounts and identify accounts with Gaia OS shell access that should not have it, reducing the pool of users who could leverage this flaw.
  • Network exposure assessment: While the socket itself is local, identifying Check Point management interfaces exposed to untrusted network segments helps gauge how easily an attacker who has already compromised another host could pivot to gain local access on the appliance.
  • Log and telemetry review: Forensic or threat-hunting exercises examining Gaia OS system logs for anomalous socket connections or unexpected root-process spawning can detect post-exploitation indicators.

Organizations that perform regular external penetration testing and authenticated internal assessments are best positioned to detect unpatched Gaia OS instances and verify that applied fixes are functioning as intended.

Sources & further reading: NVD CVE-2026-123039 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: support.checkpoint.com, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

Does an attacker need physical or remote access to exploit CVE-2026-123039?

No remote access over the network is required. The vulnerability has a Local attack vector, meaning the attacker must already hold a valid authenticated session on the Gaia OS system — for example, via SSH or a local console — before they can abuse the world-writable socket to escalate to root.

Which specific Check Point products are confirmed affected?

CISA and Check Point identify the following product families: Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway, and Security Management Server — all running Gaia OS. Exact version ranges are detailed in Check Point's official security advisory, which should be your authoritative source for scope.

Is this vulnerability being actively exploited?

Yes. CISA added CVE-2026-123039 to the Known Exploited Vulnerabilities catalog on 2026-11-13, which indicates confirmed exploitation in the wild. Organizations should treat this as an urgent remediation priority rather than a routine patch cycle item.

What if a patch is not yet available for my specific Check Point version?

CISA's BOD 26-04 required action states that if mitigations are unavailable, organizations should consider discontinuing use of the affected product. In practice, immediately restrict local account access to the minimum necessary, monitor for anomalous socket or process activity on Gaia OS, and work with Check Point support to obtain a hotfix or interim workaround as quickly as possible.