Check Point Gaia root flaw exploited, added to CISA KEV (CVE-2026-123039)

Check Point Gaia root flaw exploited, added to CISA KEV (CVE-2026-123039)

At a glance

SeverityCRITICAL
CVSSCVE-2026-123039: 7.8
EPSS (30-day exploit probability)CVE-2026-123039: 2.2%
In CISA KEV (exploited)Yes, due 2026-11-16
VendorCheck Point
CVE IDsCVE-2026-123039

Primary-source details

  • CVE-2026-123039: CVSS 7.8 (High), per NVD; a fixed version has not been published; added to the CISA KEV catalog on 2026-11-13, remediation due 2026-11-16.

CISA has added a Check Point Gaia OS privilege-escalation flaw, CVE-2026-123039, to its Known Exploited Vulnerabilities (KEV) catalog, which means it is being exploited in the wild. This Check Point vulnerability lets an authenticated local user run commands as root, and federal agencies have until 2026-11-16 to apply mitigations, according to the CISA KEV entry.

What happened

CISA listed the flaw on 2026-11-13. The catalog names it “Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability” and ties it to Check Point Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway and Security Management Server.

The root cause is the Gaia OS DynamicCLI daemon. It runs as root and listens on a local socket at /tmp/dynamic_socket that any user can write to. It does not check who is connecting, so a low-privileged user can send a command to the socket and have it executed with root rights.

NVD published the record on 2026-11-12. Check Point’s own reference for the issue is sk1000362.

Am I affected?

The products named in the KEV entry are:

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

The NVD record does not list affected version ranges, and no fixed version has been published in the data available for this story. Check the Check Point advisory for the exact builds and any hotfix guidance that applies to your appliances.

Technical details

  • Weakness: CWE-732 (incorrect permission assignment for a critical resource) and CWE-862 (missing authorization).
  • CVSS: 7.8, High. The vector is local access, low complexity, low privileges, no user interaction, with high impact on confidentiality, integrity and availability.
  • EPSS: 0.02191, a low modelled probability of exploitation in the next 30 days, even though exploitation has been observed.
  • KEV: added 2026-11-13, due 2026-11-16.
  • Ransomware use: CISA lists known ransomware campaign use as unknown.

The attack needs local access. The vector is local, and the description says an authenticated local user is required, so an attacker must already have a foothold such as a low-privileged account or a shell on the device. Details of the observed attacks, including who is exploiting it, have not been published.

Why this matters

Analysis, not new facts. A local-only flaw can look low priority, but security gateways and management servers hold firewall policy, VPN configuration and credentials. Root on one of these devices lets an attacker change rules, read secrets and hide their tracks. Chained with any other bug or a stolen admin login, a local root flaw becomes a full takeover of the perimeter.

A KEV listing means exploitation is already happening. The low EPSS figure should not lower your priority: EPSS is a prediction, and KEV is evidence. Treat this as a patch-within-hours item for any exposed or shared-admin appliance.

What to do

  1. Open the Check Point advisory and apply the mitigations it describes. CISA’s required action is to apply vendor mitigations and, where none are available, to stop using the product.
  2. Inventory every Gaia-based gateway, management server and scalable platform, including Multi-Domain servers and lab or backup units.
  3. Limit who can log in to the OS shell. Remove unused local accounts and review who holds expert-mode or SSH access.
  4. Restrict management-plane access to a dedicated admin network and require strong authentication.
  5. Treat any device where untrusted users had shell access as potentially compromised and follow CISA’s forensic triage guidance.

Detection and hunting ideas

These ideas follow from the vulnerability description, not from published indicators, since none have been released:

  • Look for processes that write to or connect to /tmp/dynamic_socket from non-administrative user sessions.
  • Review shell and SSH login history on Gaia devices for unfamiliar accounts, odd hours or unexpected source addresses.
  • Alert on new root-owned processes spawned by the DynamicCLI daemon that you do not recognise.
  • Compare current firewall policy, user lists and scheduled tasks with a known-good backup.
  • Check for new local users, changed SSH keys and altered startup scripts after any suspicious login.

What we do not know yet

Check Point has not published a fixed version in the data we can cite here, and the identity of the attackers and the scale of exploitation have not been disclosed. CISA lists ransomware use as unknown. We will update this post if CISA, NVD or Check Point add details.

Related free tool: planning network segmentation or access rules for exposed devices? Our Subnet Calculator shows network ranges, masks and usable hosts for any CIDR block.

Related coverage

Sources

Spotted an error or outdated detail? Email contact@cyberstrikenews.com with the article link. We correct and note every change. Read our Editorial Policy.

Similar Posts