CVE-2026-123039: Check Point Gaia Flaw Exploited

The United States Cybersecurity and Infrastructure Security Agency (CISA) has added a Check Point privilege-escalation flaw to its Known Exploited Vulnerabilities catalogue, giving federal civilian agencies until Monday 16 November 2026 to fix it. The flaw, tracked as CVE-2026-123039, was used by attackers to take full root control of unpatched Check Point Security Gateways and, in some cases, to wipe virtual servers behind them.
Check Point says it observed active exploitation against a couple of dozen customers, and CISA's listing confirms the vulnerability is being abused in real attacks. The flaw carries a CVSS 3.1 score of 7.8, rated High, and CISA lists known ransomware use as unknown.
What the flaw does
The bug sits in the DynamicCLI daemon of Check Point's Gaia operating system, which runs as root and listens on a local socket, /tmp/dynamic_socket. That socket was world-writable and did not check who was connecting to it, so any authenticated local user could send it a command and have that command run as root. The weakness is classified as CWE-862, missing authorisation, and CWE-732, incorrect permission assignment for a critical resource.
On its own the flaw is local-only, which is why its score is 7.8 rather than critical. But in the attacks Check Point investigated, it was the second step in a chain: once attackers had code running on the gateway, this flaw handed them root and removed every remaining barrier inside the appliance.
How attackers used it
Check Point Research says the campaign began on 30 October 2026, first targeting Israeli organisations, with a second wave on 2 November reaching organisations in several countries and sectors. The way in was the Mobile Access portal, through PHP2Shell, a pair of PHP flaws tracked as CVE-2026-109618 and CVE-2026-109619. Check Point says fixes for the entry point had been available for about a week before the attacks began.
Once inside, the attackers used CVE-2026-123039 to move from the portal's service account to root. They then planted PHP webshells and a previously undocumented backdoor called TSGA, with an embedded networking component called TSProxy. From the compromised gateway they moved over SSH to a VMware ESXi host and ran a wiper named destroy_v6, leaving politically themed notes titled DREAM_ANNEXATION.txt in directories the wiper processed.
Check Point says the scale was limited, with only a couple of dozen unpatched systems in a single region compromised in the incidents it observed, and no destructive activity was seen in the second wave. Attribution is unresolved: Check Point notes that TSGA and TSProxy share code and cryptographic material with PhiliKit, tooling previously linked by ESET to the China-nexus cluster UNC5221, but says the evidence is not enough to attribute this campaign confidently.
Who is affected and how to fix it
The flaw affects Check Point Quantum Security Gateways and Quantum Security Management systems on R82.20, R82.10, R82, R81.20 and the end-of-support R81.10 and R81 releases, across Force Firewalls, management and log servers, Multi-Domain servers and Maestro Orchestrator. The fix is in the November Jumbo Hotfix Accumulators: R82.20 Take 14, R82.10 Take 52, R82 Take 132 and R81.20 Take 174, the same takes that carry the PHP2Shell fix.
Check Point recommends installing the November Jumbo Hotfix on all management servers and security gateways, starting with internet-facing Mobile Access portals, and then running its compromise checks. CISA's listing also requires forensic triage under its BOD 26-04 directive, so affected organisations should not simply patch and move on: they should check for webshells, the TSGA backdoor and signs of lateral movement to virtualisation hosts before declaring the incident closed.