VulnerabilitiesNetwork SecurityCompetitive

Check Point Gateways: PHP2Shell In, DynamicCLI to Root, and a Wiper on ESXi

November 17, 2026 · Brian Deitch

Disclosure up front: I work at Zscaler, and Check Point competes with us in network security. Everything below comes from public reporting on Check Point's own advisory and research, linked at the end. I'm late on this one: CISA's federal deadline was yesterday, November 16.

I covered PHP2Shell on Palo Alto's PAN-OS last month. This is the same PHP bug showing up on another vendor's gateway, with a second-stage bug that turned a foothold into root.

What We Know

  • The bug: CVE-2026-123039, a local privilege escalation in Check Point Gaia OS. The DynamicCLI daemon (dynamic_server) runs as root and listens on a local socket without checking who's connecting, so any local user or code already running on the box can get root. CVSS 7.8.
  • Affected: Check Point gateways and management servers on Gaia, including Quantum Security Gateway and Security Management.
  • The chain: attackers got in through PHP2Shell (CVE-2026-109618 and CVE-2026-109619) on exposed web services like the Mobile Access Portal, then used CVE-2026-123039 to become root.
  • Timeline: PHP fixes October 21; a Check Point hotfix for the PHP issue October 23; attack waves October 30 (targeting Israeli organizations) and November 2 (multiple countries and sectors); activity stopped around November 4; Check Point disclosed the DynamicCLI bug and shipped the fix November 12; CISA added it to KEV November 13.
  • Scale: Check Point puts it at "a couple of dozen customers" in a single region, per Safeguard's reporting.
  • What attackers did: PHP webshells, a backdoor (TSGA) and proxy component, config theft and log tampering, internal recon, and lateral movement. In at least one intrusion, they SSH'd from the gateway to a VMware ESXi host and ran a Linux wiper (destroy_v6). Check Point found no destructive activity in the second wave.
  • Attribution: none with confidence. Check Point Research notes similarities to tooling ESET links to a China-nexus group, and also lists false-flag and access-broker possibilities. Its words: "the evidence does not allow us to assess with high confidence the true nature of this operation."

Credit Where It's Due

Check Point Research investigated publicly, shared indicators, laid out what it doesn't know about attribution instead of overclaiming, and shipped fixes across supported branches. That's what you want from a vendor in the middle of an active campaign.

The Architecture Point

Same lesson as with PAN-OS, and it applies to every vendor, including mine: an internet-facing gateway that runs a web stack is a server. PHP2Shell is a PHP bug, not a Check Point bug, but it landed on a box that sits at the edge with a path to the hypervisors. Once the attacker had root on the gateway, it was a trusted launch point into ESXi.

The less your security appliances expose to the internet, and the less they can reach internally, the less any one bug can do. That's the core argument for keeping inbound attack surface as close to zero as you can.

What To Do If You Run Check Point

  • Install the November Jumbo Hotfix Accumulator on gateways and management servers. Reported minimum takes: R82.20 Take 14, R82.10 Take 52, R82 Take 132, R81.20 Take 174. Confirm against Check Point's sk for your version.
  • R81.10 and older: upgrade to a supported release. No fix is listed.
  • Can't patch yet? Check Point's community guidance is to stop dynamic_server and keep it from restarting, if you can live without Dynamic CLI.
  • Limit exposure: management (Gaia Portal, SSH, SmartConsole) on a management network only. Minimize internet exposure of Mobile Access, VPN portals, captive portals and UserCheck.
  • Hunt, because patching doesn't evict anyone: PHP session files containing upload_progress_pwn, unexpected zz*.tpl or challenge_render.tpl templates, /lib/libcpfwcommon.so, listeners on TCP 11072, odd tools in /tmp, and gaps in logging.
  • Look past the gateway: SSH from gateway IPs to ESXi, unexpected use of the vpxuser account, and admin activity on vCenter and backups. If you find anything, treat the gateway as compromised and rotate every credential it held.

Bottom Line

Patch it, wall it off, and go hunting. The bug that let them in was a PHP flaw half the industry shipped. The thing that made it hurt was where it landed.

Sources: eSecurity Planet, Field Effect, Cybersecurity Dive, Safeguard, CISA KEV alert

check-pointgaiacve-2026-123039php2shellcve-2026-109618cisa-kevprivilege-escalationwiperesxiappliances
All postsDiscuss on LinkedIn