Alert

Logo de Check Point

Alert 2026-167 Root privilege escalation in Check Point Gaia exploited with PHP2Shell

Affected product(s): 

Product (CVE-2026-123039)Affected versionsFix
Quantum Security Gateway / Force Firewalls, Management and Log servers, Multi-Domain and Maestro OrchestratorR82.20, R82.10, R82, R81.20, R81.10 (end of support) and R81 (end of support)Jumbo Hotfix Accumulator: R82.20 Take 14 or later; R82.10 Take 52 or later; R82 Take 132 or later; R81.20 Take 174 or later. No Take is published for R81.10 or R81: mitigate and upgrade the branch
Product (PHP2Shell)Affected versionsFix
Force Firewalls / Security Gateway and Cloud Firewalls, if they use the portal, VPN, Captive Portal, UserCheck or Zero Phishing featuresR81.20, R82, R82.10, R82.20; end of support: R80, R80.10, R80.20, R80.30, R80.40, R81 and R81.10The same November Jumbo. Alternative: the standalone PHP2Shell hotfix (available since Oct 23; R81.10 since Oct 29); it does not close the root escalation
Spark FirewallsR81.10.x and R82.00.x; end of support: R77.20.x and R80.20.x. Not affected by CVE-2026-123039R82.00.11 starting from B998002843; R81.10.17 starting from B996005005

Spark Firewalls and Smart-1 Cloud are not affected by CVE-2026-123039; Spark may be affected by PHP2Shell. Management and Log servers and Maestro Orchestrator are not impacted by PHP2Shell, but they are by the root escalation. PHP2Shell applies when the features listed by the vendor are in use; in the observed incidents, initial access was through an internet-facing Mobile Access portal.

Description

An actively exploited attack chain against Check Point products running Gaia OS has been reported. Initial access abuses the PHP flaws identified as CVE-2026-109618 and CVE-2026-109619 (PHP2Shell), rated CVSS 9.2, critical, which may allow unauthenticated remote code execution through firewall web interfaces. That is followed by CVE-2026-123039, a local privilege escalation to root in Gaia that the vendor rates CVSS 7.8, high. The latter is not, on its own, remote code execution: the attacker must already have local code execution on the appliance. This bulletin covers the exploited chain, not only the local flaw, and is classified as CRITICAL. The PHP flaws were already covered in general terms in Alert 2026-117. Product coverage appears in Alert 2026-125 (PAN-OS) and in Alert 2026-165 (Trend Micro).

In CVE-2026-123039, the dynamic_server process (Dynamic CLI) runs as root and listens on the local IPC socket /tmp/dynamic_socket. On affected products the socket is created world-writable and does not authenticate the connecting process; it executes as root any command string it receives. The vendor notice (sk1000362) was created on Nov 8, 2026 and updated on Nov 12, 2026, the same day the CVE was published (Nov 12, 2026 at 11:02 PYT). The vendor stated that it observed active exploitation of this vulnerability against a couple of dozen customers and, in its public notice, that the compromised systems observed were a couple of dozen unpatched systems, in a single region.

On Check Point products, PHP2Shell affects Force Firewalls, Spark Firewalls and Cloud Firewalls when they use one or more of these features: the Mobile Access portal (not applicable to Spark), Remote Access VPN with SSL Network Extender (not applicable to Spark), Remote Access VPN with SAML Realm authentication, Identity Awareness Captive Portal, UserCheck Portal or Zero Phishing. The product notice is sk1000302, updated on Nov 12, 2026. Security Management and Log servers, and Maestro Orchestrator, are not impacted by PHP2Shell; the vendor Portal and SaaS services, according to that notice, were already patched.

The vendor investigated the chained exploitation against internet-facing gateways. Activity dates back to Oct 30, 2026 and was observed as active until Nov 4, 2026. In the observed incidents, initial access was through the Mobile Access portal, as the portal service account; the attackers then escalated to root with CVE-2026-123039. The standalone PHP2Shell hotfix had been available since Oct 23, 2026 at 3:30 p.m. (PYT), about one week before the attacks started; that hotfix closes the remote entry point, but it does not fix the root escalation. Organizations that installed only that hotfix remain exposed to the escalation if an attacker obtains local code execution by another path. The fix for CVE-2026-123039 is in the November Jumbo Hotfix Accumulator, whose notices were updated on Nov 12, 2026 and which also includes the PHP2Shell fix.

The vendor described a first wave on Oct 30, 2026, directed at organizations in Israel, which in some cases included destructive activity, and a broader second wave on Nov 2, 2026, across several countries and sectors, also retargeting some organizations from the first wave, with no evidence of destructive activity and no clear sector preference; it describes this as opportunistic initial-access attempts. Affected customers, according to the vendor, were notified on the day the investigation started. In a limited number of cases the activity was destructive and ideologically motivated: a scanner was deployed on the gateway, the attackers pivoted over SSH to a VMware ESXi host and ran a wiper, leaving politically themed notes that refuse to negotiate a ransom; the vendor does not describe a payment demand. The vendor does not assign a high-confidence attribution to this operation.

After obtaining root, according to the vendor, the attackers placed PHP webshells in Mobile Access portal login templates and established persistence with a backdoor launched as a component that masquerades as an appliance service, plus a shared library injected into appliance processes. The patch does not undo a prior compromise. The same November Jumbo also includes other fixes described in the vendor’s notices, which are not the subject of this bulletin and for which the vendor did not report exploitation in the wild.

Mitigation

The priority, according to the vendor, is to install the November Jumbo Hotfix Accumulator on all Security Gateways and management servers, starting with internet-facing Mobile Access deployments.

If that Jumbo cannot be installed yet, apply the standalone PHP2Shell hotfix (sk1000302) and stop dynamic_server so that both stages of the chain are covered. The PHP2Shell hotfix is installed on each gateway, cluster member, Security Group or standalone system, requires a reboot and is compatible with all Jumbo Takes. Packages exist for R82.20, R82.10, R82, R81.20 and R81.10 (the last of these since Oct 29, 2026 at 8:30 a.m. PYT). On R81.20, if Mobile Access is used, that hotfix must be installed on top of Jumbo Take 166 or later. This hotfix does not close CVE-2026-123039.

To stop dynamic_server and prevent it from restarting, the vendor publishes these commands:

dbset process:dynamic_server
dbset :save

Stopping the process causes the Dynamic CLI commands listed in sk144112 to fail. To re-enable it: dbset process:dynamic_server t and dbset :save. Do not invent an off value. Whether the process is still running can be checked, in Expert mode, with ps auxw | grep -v grep | grep 'dynamic_server'.

Until the patch is applied, there is also the mitigation of blocking requests with a multipart Content-Type in cp-httpd.conf and restarting the portals, described in sk1000302; the procedure varies by branch and that block must be removed before the hotfix is installed. On R82.20, the vendor states that the firewall protects itself with the IPS signature “PHP Remote Code Execution” even when IPS and HTTPS Inspection are not active; it makes that claim only for R82.20, it does not replace the patch, and it does not cover CVE-2026-123039.

These measures do not replace the complete update. The patch does not undo a prior compromise: indicators should be hunted, and Dynamic CLI logs, portal templates and unexpected binaries reviewed, before the incident is considered closed.

Detection

The vendor published indicators of compromise. The absence of a match does not rule out a compromise; a match warrants immediate investigation.

Network and artifacts

  • Scanning or reconnaissance source IP addresses: 130.94.19[.]204 and 130.94.19[.]168.
  • PHP session files containing the string upload_progress_pwn. In one of the intrusions analyzed by the vendor, those sessions appeared under /opt/CPcvpn-R81.20/tmp/ and the portal’s Apache/PHP workers had hundreds of segmentation faults.
  • A process or binary masquerading as a legitimate component with the CPconfigdaemon name pattern (/tmp/CPconfigdaemon, slot_CPconfigdaemon).
  • Scanning or wiper tools under /tmp or /temp, with scanner or wiper in the name.
  • A ransom-style note referring to “Dream Annexation”, with no payment demand (DREAM_ANNEXATION.txt).
  • Unexplained gaps in firewall traffic logs, particularly after a crash of the logging daemon.
  • Additional paths and names: /lib/libcpfwcommon.so, /tmp/.bd.log, /tmp/.up.tpl, and zz*.tpl and challenge_render.tpl templates in the Mobile Access login template directory.

SHA-256 hashes (observed campaign)

The following hashes were published by the vendor in the Nov 12, 2026 analysis, as artifacts of the observed campaign:

SHA-256Name / role
edb3e92eb7bda7413a09edcc4b1ba3cbed4bcdf42808a8abce63b6e4c3fda2b3.tpl webshell
4171b521fa6441382aa2fa014a08e18ff9a6e0ab6096c9144072bf46b37a2ec8slot_CPconfigdaemon
d7549671c7189979f0624ec52dad9ea6a707d23146e3585ab8f8c4720eca0c63CPconfigdaemon
3b51080a909023f7d484e2443740b572307ce0054eb9e32d98f0a06bfcd2db90gogo (scanner)
c7d9477309fac6c638a1128442056a242de086996add8cb49cd6496c36003237destroy_v6 (wiper)
0522937c0c0337be54fe25493539e5f5f8ceb9742c980aaff1cfc9515f3a96f7DREAM_ANNEXATION.txt

Dynamic CLI logs

The vulnerable daemon logs every command it receives to /var/log/dynamicCli.log. Legitimate requests use a Clish wrapper; any command that does not use it warrants investigation. After the patch is applied, rejected unauthenticated calls appear as Rejected connection from unauthorized uid (an unexpected UID, for example 99, indicates a blocked attempt). The fixed socket should appear as srw-rw---- root config (0660), not world-writable. The details of the checks are in sk1000362.

Solution

The solution is to install the November Jumbo Hotfix Accumulator on each affected Security Gateway and management server: R82.20 Take 14 or later, R82.10 Take 52 or later, R82 Take 132 or later, or R81.20 Take 174 or later. On Spark, apply R82.00.11 starting from B998002843 or R81.10.17 starting from B996005005 for PHP2Shell. On R81.10 and R81 there is no published fix for CVE-2026-123039: keep the dynamic_server mitigation in place and upgrade to a branch that has a Jumbo. Verify the installed Take and, for CVE-2026-123039, the permissions of /tmp/dynamic_socket (0660) and the indicators of compromise. The notice and packages for the standalone PHP2Shell hotfix are in sk1000302:

https://support.checkpoint.com/results/sk/sk1000302

For information on how to update, visit the following link:

https://support.checkpoint.com/results/sk/sk1000362

Additional information: