Published 17 November 2026 · Rathish Kumar, Invitty
Check Point's Gaia operating system has an exploited flaw, CVE-2026-123039, that lets any local user become root. Check Point published advisory sk1000362 on 8 November 2026 and CISA added the bug to its exploited list on 13 November. It reaches Force firewalls, Maestro, Multi-Domain servers and management servers on every Gaia release from R81 to R82.20. Install the November Jumbo Hotfix take for your version now, then check the logs for signs of misuse.
What went wrong in Gaia
The bug sits in Dynamic CLI, the service behind some Clish commands. A root process called dynamic_server listens on a local socket at /tmp/dynamic_socket. That socket was readable and writable by every user on the box, and the server did not check who was calling. Anyone with a shell on the appliance could pass it a command, and the server would execute it with root rights. Check Point scores it 7.8.
A local bug sounds less urgent than a remote one. Here it is not, because attackers already had a way in. Researchers at Rescana and others describe a chain that starts with PHP2Shell (CVE-2026-109618 and CVE-2026-109619) on the Mobile Access portal, gets a low-privilege shell, then uses CVE-2026-123039 to take root. Check Point says roughly two dozen customers were hit. Reports say some of those intrusions were destructive. PHP2Shell itself has had a hotfix (sk1000302) since 23 October, so gateways that missed that one are the most exposed.
Which Check Point products and versions are affected?
On the affected list: Force firewalls (the gateways), Maestro Orchestrator, Multi-Domain Security Management with its Multi-Domain Log Server, and the regular management and log servers. Two products are out of scope: Spark firewalls and Smart-1 Cloud. Here is where each Gaia version stands, according to sk1000362 as last updated on 12 November.
| Gaia version | Status | Fixed from |
|---|---|---|
| R82.20 | Supported | Jumbo Hotfix Take 14 |
| R82.10 | Supported | Jumbo Hotfix Take 52 |
| R82 | Supported | Jumbo Hotfix Take 132 |
| R81.20 | Supported | Jumbo Hotfix Take 174 |
| R81.10 and R81 | End of support | No fix. Workaround only, then upgrade |
To see which take you run, use cpinfo -y all in Expert mode, or show installer packages in Clish. Remember the management server. Many teams patch gateways and forget the Smart-1 or open server that manages them, and it is on the affected list too.
What to do, in order
- Confirm the PHP2Shell hotfix (sk1000302) on every gateway with a web portal, especially Mobile Access. That closes the front door.
- Install the November Jumbo take from the table on gateways, cluster members and management servers. Start with internet-facing gateways that run Mobile Access.
- Check the socket permissions. After the fix, list the socket with
ls -l /tmp/dynamic_socket. The permissions should read srw-rw----, with root as owner and config as group. If you still see srwxrwxrwx, the fix is not in. - Hunt in /var/log/dynamicCli.log. Check Point lists what to look for: commands without the normal Clish wrapper, any line containing
Received = #return_value#, and commands such as whoami, useradd, curl, wget or edits to authorized_keys. - Look for new admin accounts and policy changes you did not make during late October and early November.
Patching does not undo a compromise. If any of the hunting steps finds something, treat the box as breached: preserve the logs, rebuild from a known-good image, and rotate every credential the device held, including VPN and LDAP service accounts.
Still on R81.10 or R81?
There is no fix coming. Check Point's only measure for these versions is to stop dynamic_server and stop it restarting, using the dbset commands in sk1000362. That breaks the Dynamic CLI commands listed in sk144112, so test admin workflows afterwards. Treat the workaround as a bridge to an upgrade, not a resting place. If the appliance hardware cannot run R81.20 or later, this is the point to budget a replacement rather than keep an end-of-support gateway at the edge of your network.
What this means for Indian organisations
If the hunt shows signs of compromise, CERT-In's directions require you to report the incident within six hours of noticing it. Firewall compromise counts. Have the log excerpts and timestamps ready before you file. Separately, an upgrade from R81.10 usually needs a current support contract to download the newer release. If your Check Point support has lapsed, renew it first, and ask for a GST invoice that lists the appliance serial numbers so the cover is traceable at audit.
Next step
Send us the output of cpinfo -y all or just the model and Gaia version of each gateway and management server. We will tell you which take each one needs, whether Mobile Access exposure raises its priority, and whether any box needs an upgrade path rather than a hotfix. We support and renew Check Point firewalls, and our renewals team can check support status on every serial. More on the range is on our Check Point brand page.
Questions about Check Point CVE-2026-123039
Is CVE-2026-123039 being exploited?
Are Check Point Spark firewalls affected?
How do I confirm the fix is installed?
We are on R81.10. What are our options?
Not sure if your devices are affected? Send us the model and current firmware or version on WhatsApp, or use the form on this page. We will tell you whether this advisory applies to you and which update to schedule.
Sources
Facts in this post come from these pages, checked on 17 November 2026. Check Point updates its SK articles as new takes ship, so confirm the take for your version on sk1000362 before you schedule work.
- Check Point sk1000362: CVE-2026-123039 Gaia Dynamic CLI privilege escalation (updated 12 November 2026)
- CISA: two known exploited vulnerabilities added to the catalog (13 November 2026)
- Rescana: Check Point Gaia CVE-2026-123039 exploit chain and mitigation (14 November 2026)
- Safeguard: Check Point Gaia CVE-2026-123039 fixes and hunting commands (14 November 2026)