ZeroDayAlert

CVE-2026-123039: Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability

Check Point Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway, and Security Management Server contain an incorrect permissions assignment for critical resources vulnerability when the Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket without authenticating connecting processes. An authenticated local user can send a command to the socket and have it executed as root.

Check Point Multiple Products Added to KEV 2026-11-13 Federal due 2026-11-16 Known ransomware use

Required action — quoted from CISA

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Where this comes from. The identifier, product, dates and required action above are copied verbatim from the CISA Known Exploited Vulnerabilities catalog. The action plan below is written by an AI agent from that record and published automatically. AssurePort has not independently tested this vulnerability and makes no claim about whether any specific system is affected.

Who is affected

This vulnerability affects Check Point's Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway, and Security Management Server products running Gaia OS. The flaw lies in the DynamicCLI daemon, which runs with root privileges and listens on a local socket that any user on the system can write to, without checking the identity of the connecting process. An authenticated local user—someone with a shell account on the system—can exploit this to run arbitrary commands as root.

How to check whether this touches you

  • Inventory step: identify whether you operate any Check Point Firewall, Management Server, Security Gateway, or Scalable Platform appliances or VMs in your infrastructure.
  • Local access scope: establish whether unprivileged local user accounts exist on these systems (for example, service accounts, administrative user shells, or SSH access granted to support personnel). If the system permits only direct root or restricted administrative login, local attack surface is narrower.
  • Daemon presence and binding: query the running system for the DynamicCLI daemon and confirm it is listening on a local socket; Check Point documentation or vendor guidance will specify the socket path and how to verify its permissions.
  • Gaia OS version: confirm the Gaia OS version running on the affected appliance. Backported fixes may exist in maintenance releases, so version alone is a signal, not definitive proof of vulnerability.

What to do

  1. Immediate: request Check Point's specific patch or mitigation guidance for your product version, referencing CVE-2026-123039 and CISA BOD 26-04 compliance requirements. Do not assume all Check Point products have a single remediation path.
  2. If patching is delayed: restrict local shell access to these systems to essential administrators only; disable or revoke SSH or console access for non-essential accounts if operationally feasible.
  3. Network hardening: confirm that Management Servers are not directly reachable from untrusted networks; restrict inbound access to administrative interfaces to known, trusted subnets.
  4. Logging: enable and retain audit logs of all local user activity and root-level command execution on affected appliances, looking for DynamicCLI socket interactions or unexpected root commands. Log retention must cover the period back to the appliance's deployment or last verified patch date.
  5. Escalation timeline: treat this as a high-priority change. Federal systems have a due date of 16 November 2026 (three days from public disclosure); ensure your patching schedule aligns with that benchmark and your own risk tolerance.

If you find you were exposed

Review audit logs and command history on affected systems for the period before patching, paying particular attention to any root-level commands issued through the DynamicCLI socket or by non-administrative local users. Exploitation often precedes disclosure by weeks or months, so extend your hunt back to at least the appliance's last known-good state or the earliest retained logs. If local user accounts exist on your systems and you cannot confirm they were never used, assume exposure until logs prove otherwise; log retention gaps will be your limiting factor in that determination.

Get these the morning they land.

One email, only when a vulnerability is newly confirmed as exploited — the CISA record plus our action plan. No more than one a day, and nothing on quiet days.

Knowing it exists is not the same as knowing you are exposed.

This page can tell you that CVE-2026-123039 is being exploited. It cannot tell you whether Multiple Products is running somewhere of yours that is reachable. That question is what a scan answers.

Check your own surface →