All articles

NewsNovember 13, 20264 min read

Check Point Gaia: root via DynamicCLI socket (CVE-2026-123039)

CISA adds Check Point Gaia CVE-2026-123039 to the KEV catalog: a local user can run commands as root through an unprotected socket. What to do.

Closed round steel vault door with handles and bolts in the foreground

On 13 November 2026 CISA, the US cybersecurity agency, added CVE-2026-123039, affecting multiple Check Point products, to its Known Exploited Vulnerabilities (KEV) catalog. Inclusion in the catalog means CISA has evidence of real-world exploitation. According to the description published in the National Vulnerability Database (NVD), a component of Gaia OS, Check Point’s operating system, allows an already authenticated local user to have commands executed with root privileges.

This article is based on a single institutional source, the KEV catalog entry with the NVD data: all the details that follow come from there.

What happened

The CVE was published in the NVD on 12 November 2026 and updated the following day. On 13 November CISA added it to the KEV catalog as «Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability» and set 16 November 2026 as the deadline for US federal agencies to act: three days after inclusion.

The catalog does not say who is exploiting the flaw or against which targets; use in ransomware campaigns is marked as «unknown». As of the entry date, the NVD analysis is still in progress. The references include the vendor advisory sk1000362 on Check Point’s support portal.

Technical details

  • CVE: CVE-2026-123039
  • Product: Check Point Gaia OS, DynamicCLI daemon; the KEV catalog refers to «multiple products» from Check Point
  • Affected versions: not listed in the source; they are given in vendor advisory sk1000362
  • Weaknesses: CWE-732 (incorrect permission assignment for critical resource) and CWE-862 (missing authorization)
  • CVSS 3.1: 7.8 (high), vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score assigned by Check Point as CNA

The CVE description is short but precise. The Gaia OS DynamicCLI daemon:

  • runs as root;
  • listens on a local socket (/tmp/dynamic_socket) that is writable by every user on the system;
  • does not authenticate the processes that connect to it.

As a result, an authenticated local user can send a command to the socket and have it executed as root. These are the two weaknesses listed in the entry: CWE-732, because a resource that gives access to a privileged service has overly broad permissions, and CWE-862, because the daemon does not check who is asking it to run a command.

The CVSS vector clarifies the scope. The attack is local (AV:L) and requires low privileges (PR:L): on its own, the vulnerability does not open remote access, but it lets someone who already has an account on the system become root. No interaction from other users is needed (UI:N), and the impact on confidentiality, integrity and availability is rated high. In MITRE ATT&CK terms the scenario maps to T1068 – Exploitation for Privilege Escalation.

The source publishes no indicators of compromise and no details on the observed attack chain: it does not say, for example, how attackers obtained the initial local access.

Impact for European and Italian companies

The KEV catalog was created for US federal agencies, but it is one of the most widely used references for deciding what to patch first: a vulnerability listed there is being exploited, not just theoretical. The three-day deadline set by CISA shows the priority the agency gives it.

The scope covers anyone using Check Point products based on Gaia OS. Privilege escalation on a security appliance carries particular weight: whoever gets root on such a system controls its configuration. For entities covered by NIS2, vulnerability management and access control on critical systems are part of the required risk-management measures; the same applies to healthcare organisations, where network appliances protect clinical systems and health data.

What to do now

  1. Inventory. Identify all Check Point systems running Gaia OS, including those managed by suppliers, and record the version and role of each.
  2. Vendor advisory. Read Check Point advisory sk1000362: it lists the affected products and versions and the available fixes or mitigations. Apply them following the vendor’s instructions.
  3. CISA guidance. CISA asks organisations to apply the vendor’s mitigations and, if none are available, to stop using the product; it also asks them to assess the internet exposure of each appliance.
  4. Local access. Since the attack requires an authenticated user on the system, review who has an account on these appliances: remove unnecessary ones and restrict access to the management interfaces to authorised networks and people only.
  5. After-the-fact checks. CISA’s required action also points to its forensic triage requirements: besides patching, review access and administrative session logs for activity that cannot be traced to your administrators.

How ARXDOME can help

ARX Sentry collects logs from firewalls and other network devices and, for firewalls from the main vendors, shows dedicated pages with policies and firmware status: a help in spotting which appliances have fallen behind on updates. ARX Horizon brings threat intelligence into a single place, so events can be read alongside information on current threats.

Last updated:

Any questions?

Let’s talk about your company’s needs, with no obligation.

Contact us

Related articles