Attackers have turned vulnerabilities in Check Point security gateways into a path for persistent access and, in at least one case, destructive malware.
The US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-123039 to its Known Exploited Vulnerabilities catalog on Nov. 13, setting a Nov. 16 remediation deadline for covered federal agencies. The Gaia OS privilege-escalation flaw was exploited alongside two PHP2Shell vulnerabilities in attacks that gave intruders root access to compromised gateways.
Check Point has released security fixes, but installing them may not be enough for organizations already breached. Security teams should verify their patch status and investigate whether attackers established persistence or moved deeper into their networks.
CISA sets Nov. 16 deadline for exploited Check Point flaw
According to CISA's KEV catalog, CVE-2026-123039 involves incorrect permissions in Check Point's Gaia OS DynamicCLI service. The daemon runs with root privileges and accepts requests through a local socket without adequately authenticating connecting processes.
An authenticated local user can exploit the weakness to execute commands as root. Check Point assigned the vulnerability a CVSS severity score of 7.8.
CISA's listing requires covered federal agencies to follow vendor mitigation instructions and applicable forensic triage requirements under Binding Operational Directive 26-04. The Nov. 16 deadline does not apply universally to private organizations, although confirmed exploitation makes remediation urgent.
In its security advisory, Check Point reported that approximately two dozen unpatched systems in one region were compromised in the incidents it observed.
The company said security fixes had been available since Oct. 23, before the observed attacks began. It recommended installing the November Jumbo Hotfix on Security Gateways and management servers.
The warning follows other recent CISA additions involving actively exploited vulnerabilities.
PHP2Shell attacks led to root access and destructive malware
Check Point Research's technical investigation traced the first attacks to Oct. 30, when threat actors targeted Israeli organizations through vulnerable Mobile Access portals.
The attackers initially exploited two PHP2Shell vulnerabilities, CVE-2026-109618 and CVE-2026-109619, to gain access. They subsequently used CVE-2026-123039 to escalate their privileges through the DynamicCLI interface.
With root access, attackers deployed PHP webshells and installed a persistent backdoor called TSGA, alongside its TSProxy networking component.
The implants provided encrypted remote access, configuration theft capabilities, and mechanisms for interfering with firewall logs. They also allowed attackers to maintain access through compromised appliance services.
In one investigated incident, attackers moved from a compromised gateway to a VMware ESXi host over SSH. They deployed a Linux wiper called destroy_v6 that deleted files and attempted to overwrite their contents.
The researchers also observed a politically themed note named DREAM_ANNEXATION.txt.
A second wave of scanning on Nov. 2 targeted organizations across multiple countries and sectors. However, Check Point found no evidence of destructive activity associated with that later wave.
Although the malware shared characteristics with tools previously linked to China-nexus threat actors, Check Point could not confidently identify who conducted the attacks.
"Taken together, the evidence does not allow us to assess with high confidence the true nature of this operation," Check Point Research wrote.
Check Point releases fixed Jumbo Hotfix versions
Check Point's November Jumbo Hotfix release notes identify four fixed versions for CVE-2026-123039.
Gaia OS release | First fixed Jumbo Hotfix |
| R82.20 | Take 14 |
| R82.10 | Take 52 |
| R82 | Take 132 |
| R81.20 | Take 174 |
The listed updates also address the PHP2Shell vulnerabilities used for initial access in the observed attacks.
The Hacker News reported that the broader affected-version list includes R81.10 and R81. Neither release appears in the four published fixed-take entries. Administrators running these older versions should consult Check Point's support advisory for mitigation and upgrade guidance.
The vulnerability is distinct from the Check Point Security Management zero-day reported in September.
Patching alone may not eliminate signs of compromise
For organizations unable to install the hotfix immediately, Check Point offered a temporary mitigation involving the dynamic_server process.
"If the loss of Dynamic CLI functionality is acceptable, stop dynamic_server and prevent it from restarting," the company advised in its security advisory.
The workaround affects Dynamic CLI functionality and should not replace installing the appropriate security update.
Security teams should prioritize three actions:
- Verify patch status: Identify affected gateways and management systems, confirm installed Jumbo Hotfix versions, and prioritize internet-facing Mobile Access deployments.
- Investigate compromise indicators: Look for PHP session files containing upload_progress_pwn, suspicious CPconfigdaemon processes, unexpected tools under /tmp, and unexplained gaps in firewall traffic logs.
- Review possible lateral movement: Examine administrative access and connections to internal systems, including VMware ESXi hosts, particularly where vulnerable gateways were exposed during the October and November attacks.
Check Point cautioned that the absence of known indicators does not establish that a system is clean.
Installing the hotfix addresses the known vulnerability, but it does not automatically eliminate previously installed backdoors or reverse destructive activity.
Organizations with evidence of intrusion should initiate an incident response investigation and assess affected systems before returning them to normal operation.
Also read: Learn how CISA added an exploited SonicWall SSLVPN authentication bypass to its KEV catalog and what administrators must do to protect affected systems.





