English edition · cyberattaques.org in FrenchFrançais
VulnerabilityExploited

CISA flags exploited Check Point Gaia OS flaw that lets local users gain root

On 13 November 2026 CISA added CVE-2026-123039, a privilege escalation flaw in several Check Point products running Gaia OS, to its Known Exploited Vulnerabilities catalogue. It lets an authenticated local user run commands as root and matters to any organisation operating Check Point firewalls, gateways or management servers.

What to do now Illustration photo (circuit board)
CVSS severity7.8High
EPSS probability2 %
ExploitationConfirmed (CISA KEV)
PatchNone
Product
Check Point Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway, Security Management Server (Gaia OS)
Affected versions
—
CVE
CVE-2026-123039

CISA added CVE-2026-123039 to its Known Exploited Vulnerabilities catalogue on 13 November 2026, meaning the agency has evidence of exploitation in the wild. The affected products are Check Point Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway and Security Management Server.

The weakness lies in the DynamicCLI daemon of Gaia OS. The daemon runs as root and listens on a local socket that any user can write to, and it does not authenticate the processes that connect to it. Anyone with a local account on the device can therefore send a command to the socket and have it executed as root. The issue is classified as incorrect permission assignment for a critical resource combined with missing authorisation.

An attacker needs authenticated local access first, but on a firewall or management server root access amounts to full control of the system that guards or administers the network. CISA lists the flaw's use in ransomware campaigns as unknown.

US federal civilian agencies have until 16 November 2026, only three days after the listing, to act. CISA also requires its forensic triage procedures to be followed, a sign that devices may already have been compromised. The agency's instruction is to apply the vendor's mitigations, documented in Check Point support article sk1000362, or to stop using the product if no mitigation is available.

The source does not list affected or fixed Gaia OS versions, and it does not say whether Check Point has released a patch or only a workaround. Administrators should read the vendor advisory directly to confirm what applies to their deployment.

Action plan

What to do now

  1. Read Check Point support article sk1000362 and apply the vendor's mitigations to every affected Gaia OS device without delay.
  2. Check those devices for signs of compromise, such as unexpected commands run as root or unusual local sessions, following CISA's forensic triage requirements where possible.
  3. Review local accounts on your Check Point firewalls and management servers and remove or restrict any that are not strictly needed.
  4. As general good practice, limit administrative access to these devices to a dedicated management network and trusted workstations.

Sources