Networks

Security alert

Check Point firewalls are being broken into through their web portals: install the November Jumbo Hotfix

Attackers chained PHP2Shell and a new root flaw, CVE-2026-123039, against unpatched Check Point gateways, then wiped VMware hosts. Here is what is affected and what to install.

If you run Check Point firewalls, including the small Spark appliances (1500, 1600, 1800 and similar models), check your patch level this week. Check Point says attackers broke into unpatched gateways between October 30 and November 4, 2026 by chaining two flaws: PHP2Shell (CVE-2026-109618 and CVE-2026-109619) in the firewall’s web portals, then a new local privilege escalation, CVE-2026-123039, to become root. Check Point Research says that on some victims the attackers then moved over SSH to a VMware ESXi host and ran a wiper that deletes files.

The Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-123039 to its Known Exploited Vulnerabilities (KEV) catalog on November 13, 2026, with a federal due date of November 16. The two PHP2Shell flaws have been on the KEV list since October 26. Check Point says only a couple of dozen unpatched systems were compromised, but the patch for the first step has been out since October 23, so any gateway still missing it is a known target.

Check Point’s advice is short: install the November Jumbo Hotfix on every Management Server and Security Gateway, starting with gateways that have an internet-facing Mobile Access portal.

The two flaws, and who each one affects

PHP2Shell (CVE-2026-109618 and CVE-2026-109619, CVSS 9.2 each). These are flaws in PHP itself, which we covered in PHP2Shell: two critical flaws in PHP itself. Check Point’s gateways use PHP behind several of their web-facing features, so an unauthenticated attacker may be able to run code on the firewall through one of them. Check Point’s advisory (sk1000302) says a gateway is affected if it uses any of these:

  • Mobile Access Portal (not on Spark)
  • Remote Access VPN with SSL Network Extender (not on Spark)
  • Remote Access VPN with SAML Realm authentication
  • Identity Awareness Captive Portal
  • UserCheck Portal
  • Zero Phishing

Affected versions are R81.20, R82, R82.10 and R82.20, plus the end-of-support R80 through R81.10. Spark Firewalls on R81.10.x and R82.00.x are affected, as are end-of-support Spark R77.20.x and R80.20.x. Management and log servers aren’t affected by PHP2Shell, and Check Point says its own portal and SaaS services are already patched.

CVE-2026-123039 (CVSS 7.8). A background service on Gaia OS that runs the “Dynamic CLI” commands accepts commands from any local process and runs them as root. An attacker needs a foothold on the appliance first, which is exactly what PHP2Shell gave them. Check Point’s advisory (sk1000362) lists R81.20, R82, R82.10 and R82.20, plus the end-of-support R81 and R81.10, as affected. It covers Force firewalls, Management and Log Servers, Multi-Domain servers, and Maestro Orchestrator. Spark Firewalls and Smart-1 Cloud aren’t affected by this one.

So a Spark appliance needs the PHP2Shell fix, while a full Gaia gateway or management server needs the November Jumbo Hotfix for both.

What to install

Both advisories list the same minimum Jumbo Hotfix Accumulator takes for Gaia:

Version Fixed in Jumbo Hotfix take
R82.20 Take 14 or later
R82.10 Take 52 or later
R82 Take 132 or later
R81.20 Take 174 or later

For Spark Firewalls, sk1000302 lists the fix in R82.00.11 starting from build 998002843 and R81.10.17 starting from build 996005005. Download the image for your model from that advisory, and check the exact build there before you install.

If you can’t install a full Jumbo take yet, sk1000302 also has a standalone PHP2Shell hotfix for Gaia gateways. It needs a reboot, and on R81.20 with the Mobile Access Portal it must go on top of Jumbo Take 166 or higher. The standalone hotfix doesn’t fix CVE-2026-123039, so you still need the November take, or the mitigation below, for that.

R81.10 and older are end of support. Check Point released a standalone PHP2Shell hotfix for R81.10, but no Jumbo take fixes CVE-2026-123039 there. Plan the upgrade to R81.20 or later now, and use the mitigation below until then.

Check Point’s Jumbo Hotfix FAQ (sk98028) explains how to confirm the take installed on a gateway. Every member of a cluster needs the same take.

If you can’t patch right away

For PHP2Shell: sk1000302 has separate manual mitigation steps for standard firewalls, for Maestro and ElasticXL, and for Spark. Follow the procedure for your platform. Check Point also notes that R82.20 gateways are protected by its “PHP Remote Code Execution” IPS signatures even when IPS and HTTPS Inspection aren’t turned on. If you don’t need a portal (for example an old Captive Portal or UserCheck page nobody uses), turning it off removes that way in.

For CVE-2026-123039: Check Point’s mitigation is to stop the dynamic_server process and keep it from restarting. The commands from sk1000362 are:

dbset process:dynamic_server
dbset :save

This breaks the extra Dynamic CLI commands described in sk144112, so make a note to turn it back on (sk1000362 gives the commands) after you install the Jumbo take.

Check whether you were hit

Check Point lists several things to look for. These are the ones a small shop can check without special tools:

  • On each gateway, review /var/log/dynamicCli.log. sk1000362 gives three grep searches for commands that didn’t come through the normal Clish wrapper. Any match needs investigation.
  • After patching, confirm the fix took. Per sk1000362, ls -l /tmp/dynamic_socket should show permissions srw-rw---- owned by root and group config, not srwxrwxrwx.
  • Look for the files Check Point Research lists, including a process or file named like CPconfigdaemon and a note called DREAM_ANNEXATION.txt on gateways or ESXi hosts.
  • Check your VMware hosts. Review ESXi SSH logins, especially by the vpxuser account, since that’s how the attackers reached the hypervisor.
  • Search firewall logs for the scanning sources Check Point published, 130.94.19[.]204 and 130.94.19[.]168, and look for unexplained gaps in traffic logs.

Check Point says a clean result doesn’t prove a gateway wasn’t touched. If anything matches, treat the firewall as compromised: take it offline if you can, call Check Point support, and assume any credentials stored on or passed through it are exposed. Our first-hour incident guide covers the next steps.

While you’re in there

Check Point’s November advisory lists two more flaws it hasn’t seen exploited: CVE-2026-107484 (CVSS 7.3), privilege escalation in the Gaia Portal by an authenticated user (sk1000291), and CVE-2026-120490 (CVSS 3.8), a management-to-gateway access issue on R81.20 and R82 (sk1000364). Check those two advisories for their fixes while you’re planning the update. Keep the Gaia Portal and SSH reachable only from your management network, never from the internet. If an MSP manages your Check Point, send them this page and ask which take each gateway is on.

Sources

All articles