Installing a fixed Check Point build addresses CVE-2026-123039. It does not remove files, accounts or trust changes created while an attacker held root. The recovery record should show whether the appliance was merely vulnerable or actually compromised, and what evidence supports that conclusion.
This distinction is central to the documented PHP2Shell campaign, where DynamicCLI escalation followed an initial foothold and preceded webshells, backdoors, scanning and destructive action.
Vulnerability overview
The Gaia OS DynamicCLI daemon runs as root and uses the world-writable Unix socket /tmp/dynamic_socket. It does not authenticate the process that connects. A local user can send commands that execute as root.
CVE-2026-123039 has a CVSS 3.1 score of 7.8 and maps to CWE-732 and CWE-862. Check Point confirmed exploitation, and CISA added it to KEV on November 13, 2026.
Mechanism and exploitation conditions
The attacker needs a local execution context. In the investigated intrusion, PHP2Shell on Mobile Access portals supplied initial access. DynamicCLI then turned the limited portal or service position into root.
Recovery starts before cleanup. If responders delete files or restart without collecting evidence, they can lose the link between the initial access, the privilege change and the later persistence.
Impact
The documented intrusion used root access to place PHP webshells under portal template locations. The TSGA component appeared as /tmp/CPconfigdaemon and later as slot_CPconfigdaemon in a boot persistence location. TSProxy was embedded in /lib/libcpfwcommon.so.
The attackers also used a scanner, moved to a VMware ESXi host over SSH through the vpxuser account and executed a wiper. Those events depend on the victim environment, but they show the scope a rooted security appliance can create.
Affected products and scope
Review R82.20 through Take 10, R82.10 through Take 50, R82 through Take 130 and R81.20 through Take 173. Fixed takes are R82.20 Take 14, R82.10 Take 52, R82 Take 132 and R81.20 Take 174 or later.
The product scope includes Firewalls, Management and Log Servers, Multi-Domain products and Maestro Orchestrator. Migrate R81 and R81.10. Spark Firewalls and Smart-1 Cloud are not affected by this CVE.
Exposure context
ZoomEye returned 1,077,985 Check Point product fingerprints for app="Check Point" on November 23, 2026, while the CVE filter returned zero. The public count can identify visible devices, but recovery depends on internal evidence of local access and root activity.
Review local login records, DynamicCLI use, root process creation, portal template changes, unusual boot persistence, unexpected shared libraries, outbound connections and changes to policy or logging.
Remediation and mitigations
Preserve logs and volatile state under the incident response plan. Install the fixed build or migrate the system. Check the published file hashes from the research report against the appliance and search for the named paths, while recognizing that absence of those exact indicators does not prove clean status.
Validate accounts, services, configuration and scheduled tasks against a known-good baseline. Review downstream systems reachable from the appliance, especially virtualization management and remote service accounts. Rotate credentials that were available to the compromised root environment.
Do not return the appliance to full trust until the incident owner has reconciled initial access, privilege escalation, persistence, lateral movement and containment. Retain the fixed build evidence with the recovery decision. A closed CVE and a clean baseline are separate completion checks.