Skip to content
Blog

Check Point · Gaia OS · Security Gateway

Check Point Gaia CVE-2026-123039 in CISA KEV: the DynamicCLI Daemon Runs Whatever It's Sent as Root

CVE-2026-123039 (7.8): the Gaia OS DynamicCLI daemon listens as root on a world-writable socket. Added to CISA KEV on November 13, deadline November 16.

4 min readCVE-2026-123039

CVE-2026-123039 was published by NVD on November 12, 2026. CISA added it to the KEV catalog the very next day, November 13, with a deadline of November 16: three days to patch.

The flaw is easy to describe. On Gaia OS, the operating system behind Check Point gateways and management servers, the DynamicCLI daemon runs as root and listens on a world-writable local socket without checking who connects. Any authenticated local user can send it a command, and that command runs as root.

It's Check Point's second appearance in KEV this autumn, after CVE-2026-85102 and CVE-2026-93616 in September.


The Vulnerability

FieldValue
CVECVE-2026-123039
CVSS 3.1 (Check Point, CNA)7.8 (HIGH) — AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD scorenone yet (status Undergoing Analysis)
TypeIncorrect permissions on a critical resource (CWE-732), missing authorization (CWE-862)
Access requiredLocal, authenticated user
NVD publication2026-11-12
Added to CISA KEV2026-11-13
CISA deadline2026-11-16

NVD description:

The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket (/tmp/dynamic_socket) without authenticating connecting processes. An authenticated local user can send a command to the socket and have it executed as root.

Products named by CISA: Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway and Security Management Server, in other words everything that runs on Gaia.


How It Works

Three weaknesses stack up:

  1. The daemon runs as root. Anything it executes inherits those rights.
  2. The /tmp/dynamic_socket socket is world-writable. Any local process can connect, whichever account started it.
  3. No client authentication. The daemon doesn't check the caller's identity before running the command it receives.

The outcome is local privilege escalation: from a restricted Gaia account (a limited clish admin, a service account, or a compromised process) to root.

Why a local flaw ends up in KEV

A 7.8 score with AV:L drops down the list in most tools. But local escalation on a security gateway is rarely used on its own: it's how limited initial access becomes full control of the device. On a gateway, root means the filtering policy, the VPN keys and the traffic flowing through it.

Neither NVD nor CISA describes the exploitation campaign. The most likely reading is chaining: initial access gained some other way (stolen credentials, another flaw), then CVE-2026-123039 to get root. The KEV entry also requires forensic triage (BOD 26-04) on top of patching.


Affected Versions

At this stage NVD publishes no CPE configuration for this CVE: no version list and no fixed version in its data.

The reference is Check Point support article sk1000362, cited by both NVD and CISA. That's where to find the affected Gaia versions and the fix (Jumbo Hotfix or dedicated hotfix) for your release.

Check your version and installed hotfixes:

show version all
cpinfo -y all

Detection

  • Socket presence and permissions: ls -l /tmp/dynamic_socket (a world-writable socket confirms exposure)
  • Unknown or recently created local Gaia accounts, and changes to default shells
  • Unusual root processes started outside the expected Check Point daemons
  • Recent files in /tmp, /var/tmp and startup directories
  • SSH sessions to the gateway from addresses that don't normally administer it

Mitigation

1. Apply the fix from sk1000362

The CISA deadline is November 16. In a cluster, patch every member.

2. Limit who can open a local session

The flaw needs an authenticated local user: that's the barrier to harden in the meantime.

  • Inventory Gaia accounts and remove unused ones
  • Restrict SSH and WebUI to admin hosts (the Allowed Clients setting)
  • Enforce strong authentication on administrative accounts

3. If you suspect a compromise

  1. Assume the fix does not remove anything a root attacker already installed
  2. Rotate admin credentials, SIC secrets and VPN keys
  3. Compare policy and configuration against a backup from before the suspect period
  4. Follow the BOD 26-04 forensic triage requirements cited by CISA

Why Continuous Monitoring of Your Check Point Estate Matters

A local HIGH, published on a Thursday and added to KEV the next day with three days to act: without an up-to-date inventory of your gateways and their Gaia versions, the deadline is gone before you've even settled whether you're exposed.

With cveo.tech, register your Check Point devices with their versions, and get an alert as soon as a CVE affecting them enters the CISA KEV catalog.

Know which CVEs hit the versions you run.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.