Check Point Gaia OS Flaw CVE-2026-123039 Exploited
Check Point Gaia OS Flaw CVE-2026-123039 Exploited
What CVE-2026-123039 is and who it affectsCheck Point has published a vulnerability tracked as CVE-2026-123039, described officially as an incorrect p...
What CVE-2026-123039 is and who it affects
Check Point has published a vulnerability tracked as CVE-2026-123039, described officially as an incorrect permission assignment for a critical resource. The affected products are Check Point Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway and Security Management Server.

The root cause sits in the Gaia OS DynamicCLI daemon. According to the NVD entry, that daemon runs as root and listens on a world-writable local socket at /tmp/dynamic_socket without authenticating the processes that connect to it. In practice, an authenticated local user can send a command to that socket and have it executed with root privileges. The weakness maps to CWE-732 (incorrect permission assignment) and CWE-862 (missing authorisation).
NVD published the record on 12 November 2026 with a severity of CVSS 3.1 7.8, HIGH (vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Note the local attack vector: this is not a flaw reachable directly from the internet, but it is a serious one for any organisation where an attacker already holds a low-privilege account, a compromised VPN user or a foothold on an internal host. For a Spanish pyme or online shop running Check Point appliances at the edge, that means the firewall itself can become the escalation path.
Why it is urgent: already exploited in real attacks
This is not a theoretical issue. CISA added CVE-2026-123039 to its Known Exploited Vulnerabilities (KEV) catalogue on 13 November 2026, which means there is confirmed evidence of exploitation in real attacks. CISA gave US federal agencies until 16 November 2026 to remediate it.
The required action is to apply mitigations in line with the vendor's instructions, following CISA's BOD 26-04 guidance on prioritising security updates by risk and its forensics triage requirements. Where mitigations are unavailable, CISA tells agencies to discontinue use of the product, and it puts the responsibility on asset owners to assess each system's internet exposure. There is no record in the source data of this vulnerability being used in ransomware campaigns, so treat that as unconfirmed rather than ruled out.
What to do today
- Inventory first. Confirm whether your organisation runs any of the affected Check Point products and record the exact Gaia OS version on each appliance. Many companies inherit a firewall from a former provider and no longer have a clear picture of what is installed.
- Follow the vendor advisory. Check Point's support note sk1000362 is the authoritative source for the fix and any interim mitigation. Apply exactly what it specifies for your version; do not assume a particular release is patched without checking.
- Look for signs of intrusion. Because exploitation requires an authenticated local user, review local accounts, recent privilege changes, unusual command execution and any unexpected activity around the DynamicCLI service. If you find evidence of abuse, treat it as a compromise of the security appliance itself, not a minor incident.
- Reduce what is exposed. Restrict management interfaces so they are not reachable from the public internet, enforce least privilege on local accounts and review who genuinely needs shell access to the appliance.
- Document the decision. If you cannot patch immediately, record the compensating controls in place and the date by which the update will be applied. Under GDPR, an unpatched, actively exploited flaw in a perimeter device is a risk you may need to justify.
How a cybersecurity team like ALMC's can help
Most small teams in Catalonia — in Barcelona, Lleida, Tarragona or Girona — run lean IT departments where a firewall update competes with a hundred other tasks. This is where an external security team earns its keep: auditing what is actually exposed, checking versions against vendor advisories, hardening servers and appliances, and monitoring for the kind of local privilege abuse this flaw enables.
At ALMC we work with pymes and online businesses on exactly this ground: security audits and pentesting to find weaknesses before they are exploited, hardening of servers and CMS platforms such as WordPress, PrestaShop and Joomla, ongoing monitoring and incident response, and recovery when a site has already been hacked. The value is not a one-off scan but a routine that keeps patches, permissions and exposure under control — so that a CVE like this one is closed on your estate while it is still a headline, not after it has become an incident.
Related
- Ivanti Connect Secure: CVE-2026-104935 Under Active Attack
- CVE-2026-96951: Windows Shell Command Injection Under Attack
- Click to Chat for WhatsApp: CVE-2026-92097 in WordPress
- Abuse Shield
Is your business exposed to flaws like this?
ALMC checks which versions you are running, applies the patches and hardens your servers and website. Contact our team for a security review.
