11/16/2026 • Security
Check Point Gaia Root Flaw Exploited: Why 'Local' Bugs Matter
A Check Point Gaia OS flaw (CVE-2026-123039) that lets a local user become root is being actively exploited and is now on CISA's Known Exploited Vulnerabilities list. Here is what it affects, what it doesn't, and what to do about it.
A flaw that lets an ordinary local user become root on Check Point's Gaia operating system is being used in real attacks, and on 13 November 2026 the US cyber agency CISA added it to its Known Exploited Vulnerabilities (KEV) catalogue. US federal agencies were given until 16 November, just three days, to deal with it.
The flaw is CVE-2026-123039. On paper it looks like one you could leave for the next maintenance window: it is rated 7.8 (High) rather than Critical, and it cannot be triggered from the internet on its own. This post is about why that reading is wrong.
What happened, in plain English
Gaia is the operating system underneath Check Point's firewalls and management servers. One of its background services, the DynamicCLI daemon (the process is called dynamic_server), runs with full root privileges and takes instructions through a local socket.
According to Check Point's advisory (sk1000362) and the NVD record, that socket was writable by every user on the system, and the service did not check who was connecting. Any command sent to it was run as root. In practice, anyone who could run code on the appliance, even as a low-privileged user, could take complete control of it.
The details matter here, so this is what the primary sources say:
- It is not a remote, anonymous attack on its own. The CVSS vector is
AV:L/PR:L: the attacker needs local access and a low-privileged foothold first. Check Point states the prerequisite directly: the attacker must already have code execution on the appliance. - It is being exploited. Check Point says it has seen active exploitation against about two dozen customers, and CISA's KEV listing confirms exploitation in the wild.
- A fix exists for supported versions. Check Point lists fixes in Jumbo Hotfix Accumulator Take 14 for R82.20, Take 52 for R82.10, Take 132 for R82 and Take 174 for R81.20 (and later takes in each case).
- Older versions are affected and have no fix listed. R81.10 and R81 are both marked end of support in the advisory.
- Affected products are Check Point's Gaia-based firewalls (the advisory calls them Force Firewalls, and the CVE record lists Quantum Security Gateway), Management and Log Servers, Multi-Domain Security Management and Maestro Orchestrator.
- Not affected: Check Point's Spark firewalls, its small-business range, and Smart-1 Cloud. If the Check Point box in your office is a Spark appliance, this particular flaw is not yours to fix.
How attackers get that first foothold
If the attacker already needs to be on the firewall, how are they getting there?
CSO Online reports that the attackers came in through the Mobile Access portal, the remote-access web portal on the gateway, using a separate pair of PHP flaws known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). The PHP project rates both as critical (9.2), and CISA added both to the KEV catalogue on 26 October 2026. That reporting says the two have been used together since late October.
PHP2Shell gives the attacker limited code execution on the gateway. CVE-2026-123039 turns that limited access into root. With root on a firewall, an attacker can read its configuration, tamper with its logs and reach the networks it was meant to protect. CSO Online describes exactly that, including backdoors built to survive reboots.
The real lesson: don't sort your patching by score alone
The lesson applies to anyone, whether or not they own Check Point gear.
Most patching advice comes down to fixing the criticals first. That is sensible, but this case shows the gap in it. A 7.8 local flaw sat one step behind a remote one, and together they amounted to full takeover of a security appliance. Attackers combine flaws into chains, and a severity score rates only one flaw at a time.
Two habits follow from that:
- Treat severity and exploitation as separate questions. A CVSS score tells you how bad a flaw could be, and the KEV list tells you whether someone is using it right now. A High flaw on the KEV list should be patched ahead of a Critical flaw that nobody is exploiting.
- Remember that a firewall is a computer. It runs an operating system, a web server and background services like any other machine, and it sits at the most exposed point of the network. It needs the same patching discipline as your servers, and probably more.
We made a similar point about credentials and patch hygiene in our FortiBleed explainer. The vendor is different but the pattern is the same.
The honest bit
This is not a story about one bad vendor. Check Point published a clear advisory, shipped fixes, and gave administrators specific log checks to find out whether they had been hit, which is what a vendor should do. The CSO Online piece lists Fortinet, Cisco and Palo Alto Networks as having had exploited firewall or firewall-management flaws this year as well. No vendor is immune, including the ones we like and sell.
What differs between platforms is how quickly a fix reaches you. Cloud-managed platforms push fixes out automatically and publish end-of-support dates you can plan around, which narrows the window in which a business is exposed while waiting for someone to schedule an upgrade. We covered that in why a cloud-managed firewall keeps getting better after you buy it. It reduces the risk without removing it, and an appliance you patch promptly yourself is also in good shape.
What we'd suggest you actually do
If you run Check Point gear, or your IT provider does on your behalf:
- Find out what you have. Confirm the product and Gaia version. Spark appliances and Smart-1 Cloud are not affected. Gaia R81 through R82.20 is.
- Install the fixed Jumbo Hotfix take for your version, as listed in sk1000362. Check Point's advice, as reported, is to start with gateways that expose Mobile Access to the internet.
- If you can't patch today, use the interim mitigation. Check Point's advisory explains how to stop the
dynamic_serverprocess and keep it from restarting. The trade-off is that some Dynamic CLI commands stop working until you turn it back on. - Check for signs of compromise as well as patching. The advisory includes log searches against
/var/log/dynamicCli.logthat show whether the socket has been abused. Run them on any gateway that has been internet-facing since late October. A patch closes the hole, but it does not remove an attacker who is already inside. - Deal with the first link in the chain. Make sure the PHP2Shell fixes are applied, turn off Mobile Access if nobody uses it, and keep management interfaces off the internet.
- If you're on R81.10 or R81, plan the upgrade now. Those versions are end of support and have no fix listed. Our AryStinger post covers why unsupported gear at the network edge keeps turning into a target.
- Send firewall logs somewhere else. An attacker with root can edit logs stored on the device, so keep a copy on a system the firewall cannot reach. Our post on whether your network can spot an intruder has more on this.
If you don't run Check Point at all, steps 5 to 7 still apply to whatever is at the edge of your network.
The friendly takeaway
None of this is cause for panic. The flaw has a fix, the vendor has been open about it, and the small-business Spark range is not affected. If you do have affected Gaia systems, patch them this week and run the compromise checks, and don't let the word "local" push the job down the list.
If you're not sure what is running at the edge of your network, or whether it is still supported, we're happy to be a second pair of eyes. There's no obligation and no hard sell.
References
- NVD, CVE-2026-123039: https://nvd.nist.gov/vuln/detail/CVE-2026-123039
- Check Point advisory sk1000362, Local Privilege Escalation to Root via Dynamic CLI Socket: https://support.checkpoint.com/results/sk/sk1000362
- CISA Known Exploited Vulnerabilities catalogue, CVE-2026-123039: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-123039
- Canadian Centre for Cyber Security, Check Point security advisory AV26-1154: https://www.cyber.gc.ca/en/alerts-advisories/check-point-security-advisory-av26-1154
- NVD, CVE-2026-109618 (PHP2Shell): https://nvd.nist.gov/vuln/detail/CVE-2026-109618
- NVD, CVE-2026-109619 (PHP2Shell): https://nvd.nist.gov/vuln/detail/CVE-2026-109619
- CSO Online, The firewall becomes the foothold: Attackers turn Check Point gateways against customers: https://www.csoonline.com/article/4248693/the-firewall-becomes-the-foothold-attackers-turn-check-point-gateways-against-customers.html