A Check Point Gaia vulnerability, CVE-2026-123039, is being used with the PHP2Shell flaws to take full control of Check Point firewalls. CISA added it to its Known Exploited Vulnerabilities catalog on November 13, 2026, with a federal due date of November 16. Check Point says it saw the exploit used against "a couple of dozen customers."
The flaw lets anyone who already has a foothold on the appliance run commands as root. Attackers got that foothold through PHP2Shell, a PHP flaw that reaches the firewall’s web portals. In some cases they then moved to VMware ESXi hosts and ran a wiper. This post covers what the flaw is, which versions and takes fix it, the stopgap, how to check for compromise, and what to ask your MSP. Facts are as of November 16, 2026.
The short version: install the November Jumbo Hotfix on every Check Point gateway and management server. If you cannot do that tonight, stop the vulnerable process with the commands below. Then check the log Check Point names for signs that someone already used it. If an MSP runs your firewall, ask them for the installed take and the log results in writing.
What the Check Point Gaia vulnerability is
Gaia is the operating system on Check Point firewalls and management servers. Its "Dynamic CLI" adds extra commands to the Gaia shell. A root process called dynamic_server handles those commands.
Check Point’s advisory, sk1000362, explains the bug. That process listens on a local socket, /tmp/dynamic_socket. On affected versions the socket is open to every local user, and the process does not check who is connecting. It then "executes whatever command string it receives as root."
So any local account can become root by writing one request to that socket. Check Point rates the Check Point Gaia vulnerability High, with a CVSS score of 7.8. The score is lower than a remote flaw would get because the attacker needs local access first. Our guide to reading a CVSS score explains why that matters, and our CVE explainer covers the basics.
The catch is that "local access first" was easy to get here. PHP2Shell supplied it.
How attackers chained it with PHP2Shell
PHP2Shell is the name for two PHP flaws, CVE-2026-109618 and CVE-2026-109619. We covered them when they leaked in PHP2Shell: How Two Critical PHP Flaws Leaked Early. Check Point firewalls run PHP behind several web portals, so they were exposed too.
Check Point’s security advisory blog post lays out the chain:
- Attackers used PHP2Shell in the Mobile Access Portal to run code as the portal’s service account.
- They used the Check Point Gaia vulnerability to become root.
- They set up persistence on the gateway.
Check Point says exploitation "dates back to October 30" and was seen until November 4. It notes that PHP2Shell fixes had been out since October 23. "Only a couple of dozen unpatched systems, in a single region, were compromised," it says.
Check Point Research adds the detail. The first wave, from October 30, targeted Israeli organizations and included destructive activity against some of them. A broader wave on November 2 hit organizations in several countries, with no sign of destruction.
What the attackers did after getting root
According to Check Point Research, the attackers:
- Planted web shells in the portal’s template folder.
- Installed a backdoor it calls TSGA, disguised as a Check Point process named
CPconfigdaemon. Check Point Research says it offers encrypted remote access, configuration theft and firewall log tampering. - Ran a network scanner called gogo to map internal systems.
- Moved to a VMware ESXi host over SSH using the
vpxuseraccount. - Ran a wiper,
destroy_v6, on that host. It deletes files and leaves a note namedDREAM_ANNEXATION.txt.
Check Point Research links the backdoor to a toolkit tied to a China-nexus group. It also says the destruction and the Israel focus do not fit that group. Its conclusion is that the evidence does not let it judge "with high confidence the true nature of this operation." The Hacker News reported the same findings on November 13.
For small IT teams, the lesson is plain. A firewall that is breached can give access to the servers behind it, including your virtualization hosts. Our post on GlobalProtect and ransomware shows the same pattern with another vendor’s VPN.
Which versions the Check Point Gaia vulnerability affects
Check Point lists these products as affected by the Check Point Gaia vulnerability: Check Point Force Firewalls (the Quantum gateways), Management and Log Servers, Multi-Domain Security Management and Multi-Domain Log Server, and Maestro Orchestrator. Spark Firewalls and Smart-1 Cloud are not affected.
| Gaia version | Fixed in | Notes |
|---|---|---|
| R82.20 | Jumbo Hotfix Take 14 or later | Supported |
| R82.10 | Jumbo Hotfix Take 52 or later | Supported |
| R82 | Jumbo Hotfix Take 132 or later | Supported |
| R81.20 | Jumbo Hotfix Take 174 or later | Supported |
| R81.10 and R81 | No fix listed | End of support; upgrade |
The same takes also fix PHP2Shell, per Check Point’s PHP2Shell advisory sk1000302. Check Point’s blog tells customers to install the November Jumbo Hotfix "on all Management Servers and Security Gateways" and to put internet-facing Mobile Access first.
Note that the NVD entry lists only R81.20 through R82.20. Check Point’s own advisory adds R81 and R81.10. Go by Check Point.
Which gateways PHP2Shell can reach
The root flaw needs a way in. On these appliances, PHP2Shell was that way in. Per sk1000302, a gateway is exposed to PHP2Shell if it uses any of these features:
- Mobile Access Portal
- Remote Access VPN with SSL Network Extender
- Remote Access VPN with SAML Realm authentication
- Identity Awareness Captive Portal
- UserCheck Portal
- Zero Phishing
Check Point says its management and log servers are not affected by PHP2Shell. They are still affected by the Check Point Gaia vulnerability, so patch them too. Any other foothold, such as a stolen admin login, would also let an attacker use it.
If you cannot patch tonight: the stopgap
Check Point’s mitigation is to stop the dynamic_server process and keep it from restarting. From the Gaia shell, run:
dbset process:dynamic_server
dbset :save
This breaks the Dynamic CLI commands listed in Check Point’s sk144112. To turn the process back on later, run dbset process:dynamic_server t and then dbset :save. To see if it is running, use this in Expert mode: ps auxw | grep -v grep | grep 'dynamic_server'.
Treat this as a bridge to the hotfix. It does not fix PHP2Shell.
How to check a gateway for compromise
Patching closes the Check Point Gaia vulnerability, but it does not show whether someone used it. The vulnerable process logs every command it gets to /var/log/dynamicCli.log. Check Point’s sk1000362 gives three checks to run on each gateway or cluster member:
- Look for commands that do not use the normal Clish wrapper. Legitimate entries contain
CPprofile.sh >> /dev/null; export SP_DISTRIBUTE=0; set -o noglob;. Anything without it needs a closer look. - Search for
Received = #return_value#, which Check Point says is rare or absent in normal use. - Search for commands often seen in attacks, such as
whoami,/etc/shadow,wget,curl,useraddandauthorized_keys.
After patching, confirm the fix. Check Point says ls -l /tmp/dynamic_socket should show srw-rw---- root config, not srwxrwxrwx. The fixed build also logs blocked attempts as "Rejected connection from unauthorized uid."
Check Point’s blog lists other signs. These include PHP session files containing upload_progress_pwn, a process named like CPconfigdaemon, files with "scanner" or "wiper" in the name under /tmp, and unexplained gaps in firewall logs. It also lists two scanning addresses, 130.94.19.204 and 130.94.19.168. Check Point warns that no match "does not rule out compromise."
If you find signs, assume the attacker could reach anything the firewall could. That includes ESXi hosts, so check those as well.
What to ask your MSP about the Check Point Gaia vulnerability
Many nonprofits, associations and schools have a Check Point firewall that an MSP manages. You may never log in to it. That makes the questions more important. Ask in writing:
- What Gaia version and Jumbo Hotfix take are on each of our gateways and management servers? Compare the answer to the table above.
- Is Mobile Access, SSL Network Extender, SAML VPN, Captive Portal, UserCheck or Zero Phishing turned on? If yes, when was the PHP2Shell hotfix installed?
- Did you run Check Point’s checks on
/var/log/dynamicCli.log, and what did they find? - Are any of our devices on R81 or R81.10? Those are end of support, and Check Point lists no fix.
- Can the firewall reach our ESXi or other management interfaces? If so, ask whether those hosts were checked.
Our posts on N-able taking N-central offline and the MSP Process breach cover more questions to ask a provider this month.
The other KEV entry: UnrealIRCd
CISA’s November 13 alert added a second flaw, CVE-2026-114713 in UnrealIRCd, an open-source IRC chat server. Per the NVD entry, versions 6.0.0 up to 6.2.7.1 do not escape a message tag in replies. On networks with two or more linked servers, any user can inject server commands that run "with server authority."
The UnrealIRCd project released 6.2.7.1 and a hot-patch on November 7. It says the hot-patch fixes nine issues, one of them critical, and on almost all UnrealIRCd 6 networks needs no restart. Few of our readers run IRC servers. If you host one for a community or class, update it now.
Frequently Asked Questions
What is CVE-2026-123039?
A Check Point Gaia vulnerability in the Dynamic CLI process. Any local user can send a command to a world-writable socket and have it run as root.
Is it being exploited?
Yes. Check Point says it saw active exploitation against a couple of dozen customers, and CISA added it to the KEV catalog on November 13, 2026.
Can an attacker use it from the internet?
Not on its own. It needs local access first. In the attacks Check Point saw, PHP2Shell in the Mobile Access Portal provided that access.
Which Jumbo Hotfix takes fix it?
R82.20 Take 14, R82.10 Take 52, R82 Take 132 and R81.20 Take 174, or later takes. The same takes also fix PHP2Shell.
Are Spark firewalls or Smart-1 Cloud affected?
Check Point lists Spark Firewalls and Smart-1 Cloud as not affected by CVE-2026-123039. Spark Firewalls are affected by PHP2Shell, so check sk1000302.
What if we are on R81 or R81.10?
Check Point lists both as affected and end of support, with no fix listed. Plan an upgrade to a supported version and use the stopgap until then.
Does stopping dynamic_server break anything?
Yes. Dynamic CLI commands listed in sk144112 stop working. Check Point gives commands to turn the process back on after you patch.
What was the CISA due date?
November 16, 2026, for federal civilian agencies. CISA also marked the Check Point Gaia vulnerability as needing forensic triage under BOD 26-04.
What is the UnrealIRCd flaw?
CVE-2026-114713, a command injection flaw in UnrealIRCd 6 before 6.2.7.1 on networks with linked servers. Update or apply the project’s hot-patch.