Check Point has patched a flaw in Gaia, the operating system that runs its firewalls and management servers, that lets someone who is already on the device become root. The company says it has seen the flaw used against a couple of dozen customers, and on 13 November the US cybersecurity agency CISA added it to its catalogue of exploited vulnerabilities with a due date of 16 November, which is today.
The flaw, CVE-2026-123039, cannot be reached from the network on its own. That is what makes the exploitation report uncomfortable: wherever it was used, an attacker already had a way to run commands on a firewall.
What the flaw is
Check Point's advisory, sk1000362, describes it as a local privilege escalation and scores it 7.8 on the CVSS scale. The advisory was created on 8 November and last changed on 12 November.
Gaia has a feature called Dynamic CLI, which adds extra commands to the firewall's own shell. A background process that runs as root serves those commands through a local socket, a private channel between programs on the same machine. On affected versions, by Check Point's account, any local user could write to that socket and the process did not check who was calling. Whatever arrived was run as root.
CISA's entry puts the requirement plainly: an authenticated local user. A stolen low-privilege account or a foothold from another bug would be enough to turn limited access into full control of the device.
Who is affected
Check Point lists four product lines: Force Firewalls, Management and Log Servers, Multi-Domain Security Management with Multi-Domain Log Server, and Maestro Orchestrator. It says Spark Firewalls and Smart-1 Cloud are not affected.
The fix ships in the Jumbo Hotfix Accumulator, Check Point's rolling bundle of fixes. A take is one numbered build of that bundle.
| Gaia version | Fixed from |
|---|---|
| R82.20 | Take 14 |
| R82.10 | Take 52 |
| R82 | Take 132 |
| R81.20 | Take 174 |
| R81.10 | No fix listed, end of support |
| R81 | No fix listed, end of support |
The last two rows matter. Both versions are affected, and the advisory marks both as past the end of support and names no fixed take for either.
The fix and the stopgap
Check Point says the fix "blocks and logs unauthenticated calls" to the Dynamic CLI. Its own test is the socket's permissions: after the fix it is owned by root with mode 0660, where it used to be open to everyone at 0777.
Where the bundle cannot be installed at once, the advisory gives a stopgap: stop the Dynamic CLI process and keep it from starting again. The cost is the set of extra commands that depend on it, which Check Point lists in a separate article, sk144112. Take the exact commands from the advisory, not from a summary like this one.
For R81 and R81.10 the stopgap is the only measure on offer. We would treat it as a reason to bring the upgrade forward, not as a fix.
Why the deadline is so short
CISA's due dates bind only US federal civilian agencies, under a directive called BOD 26-04. Everyone else can read them as a measure of urgency, and three days is the short end. By our count of CISA's data, nine of the fifteen flaws it has added in November came with a three-day deadline, this one among them. Four of the others are covered in our post on last week's additions.
CISA's alert adds that the directive also sets expectations for checking whether an attacker was on a system before the patch went in. For this flaw that check is the important half of the job.
Check whether it was used against you
A patched system records what it refuses. Check Point points to the Dynamic CLI log, /var/log/dynamicCli.log, where a blocked attempt appears as a rejected connection from an unauthorised user ID. The advisory also gives search patterns for log entries that show commands arriving without the wrapper Gaia's own shell adds, and for commands typical of an intruder, and it recommends matching any burst of them against portal, web and authentication logs.
We read a hit differently from a failed login. Nobody reaches that socket from outside, so an attempt means someone was running code on the firewall.
What we would do first
- List every Gaia machine with its version and take. Include management and log servers. They are on Check Point's list and are easy to forget because traffic does not pass through them.
- Install the fixed take. We would start with whatever has the most accounts or the most exposure, which is usually the management server and any gateway with a web portal open to the internet.
- On R81 and R81.10, apply the stopgap today and set an upgrade date. A firewall without security fixes will meet the next flaw in the same position.
- Search the logs before closing the ticket. If the patterns in the advisory turn anything up, our advice is to treat the device as compromised: review its administrator accounts, change its credentials and find out how the attacker got on in the first place.