Published on November 17, 2026 · The mitza.es team

We summarize what is known as of November 17, 2026, based on Check Point's advisory (SK1000362), its research report of November 12 and BleepingComputer's coverage. The case brings together two pieces we have already covered separately: the PHP flaw PHP2Shell and a flaw in the operating system of the gateways themselves, Gaia.
What happened
- October 30: according to Check Point Research, exploitation of PHP2Shell (CVE-2026-109618 and CVE-2026-109619) begins against gateways with the mobile access portal (Mobile Access) exposed. The first wave hits Israeli organizations and has a destructive component. Check Point says the PHP patch had existed for about a week before the attacks began.
- November 2: second wave, against organizations in several countries, with no destructive activity.
- November 8: Check Point creates SK1000362 on the flaw that allows escalating to root in Gaia; it updates it on the 12th.
- November 12: it publishes its report on the campaign.
- November 13: CISA adds CVE-2026-123039 to its catalog of exploited vulnerabilities (with a deadline of the 16th for U.S. federal agencies).
The attack chain
- Entry: PHP2Shell, through the Mobile Access portal, gives initial access to the gateway.
- Escalation: CVE-2026-123039 allows going from a local user to root.
- Persistence: webshells in the Mobile Access templates directory and the TSGA and TSProxy backdoors.
- Lateral movement and damage: a jump to a VMware ESXi server and execution of a wiper (a program that destroys data) called
destroy_v6in the destructive cases.
Check Point observed active exploitation of CVE-2026-123039 against “a couple of dozen” customers, according to the SK itself as cited by BleepingComputer. Attribution is unclear: ESET links the tool (PhiliKit) to the group UNC5221, tied to China, but Check Point says the evidence does not allow a firm attribution and that the destructive activity, the Hebrew-language note and the name do not fit that actor; it does not rule out a false flag operation or an intermediary.
The Gaia flaw: CVE-2026-123039
It is a local privilege escalation to root in Gaia's DynamicCLI daemon (the dynamic_server process), which listens on a control socket with write permissions for any user. Any authenticated local user could run commands as administrator. Check Point scores it with a CVSS of 7.8.
Affected products and versions
- Gateways (Force Firewalls), management and log servers, Multi-Domain and Maestro Orchestrator, in versions R82.20, R82.10, R82, R81.20, R81.10 and R81.
- Does not affect Spark firewalls or Smart-1 Cloud, according to the SK. The SK does not mention Quantum SMB devices.
- R81.10 and R81 are out of support and the SK offers no fix for them: you must migrate to a supported version.
Fix: Jumbo Hotfix accumulators
- R82.20: from Take 14.
- R82.10: from Take 52.
- R82: from Take 132.
- R81.20: from Take 174.
Until you can apply it, the SK describes a mitigation that consists of stopping and disabling the dynamic_server process; follow Check Point's exact procedure and do not improvise. After the fix, the socket should have srw-rw---- root config permissions.
How to check whether you were attacked
- Review
/var/log/dynamicCli.log: commands without the normal Clish wrapper, lines withReceived = #return_value#or commands such aswhoami,/etc/shadow,curlorwget. - Look for webshells in the Mobile Access templates directory and for processes or services you don't recognize.
- Check for SSH access from the gateway to VMware ESXi servers that nobody has authorized.
- Check Point's report includes IP addresses and hashes of indicators of compromise (among them 130.94.19[.]204 and 130.94.19[.]168); check them in its original publication.
- After fixing, the line
Rejected connection from unauthorized uidin the same log indicates that the socket now rejects unauthorized users.
We have not found in the report a specific advisory or version from Check Point for the PHP2Shell part; check its support portal and confirm with your provider that the November hotfix and the PHP fix are applied.
What to do: checklist
- Find out whether you use Check Point (gateways, mobile access VPN, management servers) and which version. If a provider manages it, ask them.
- Apply the Jumbo Hotfix for your branch and check that the Mobile Access portal is not exposed to the internet unless it is essential.
- Look for signs of intrusion using the points above, especially on devices exposed since October 30.
- If there are signs, isolate the device, rotate credentials and keys (including those of ESXi and other servers it connects to) and restore from a clean configuration.
- Review the backups of the virtualization servers: a wiper is countered with copies out of its reach (3-2-1 rule).
- Replace unsupported devices (R81.10 and R81): they will not receive this fix.
What this case teaches a small business
Once again, attackers get in through the device that protects the network. We have seen it in the Ivanti Connect Secure VPN, in the Citrix NetScaler zero-days, in the Zyxel switches and in the SonicWall SSL VPN. Having an inventory of security devices, a patching deadline for exploited flaws and someone watching the advisories is what makes the difference. You have criteria in the guide to reading a security advisory and the basics in what a firewall is and what a small business needs.
Quick questions
Does it affect me if I have a firewall from another brand?
This advisory is from Check Point. But the pattern is common: ask your provider about the patching status of all your security devices.
Should I worry if I don't have the Mobile Access portal?
PHP2Shell got in through that portal, so the risk of that chain is lower without it, but the Gaia flaw affects the gateways and other products on the list even if you don't use it. Apply the fix.
How we can help at Mitza
We take an inventory of your security devices, review their version and exposure and help you ask your provider for guarantees. See our IT maintenance for small businesses service or write to us from the contact page.
Related reading: N-able N-central: exploited flaws and the HF3 patch and the NIS2 regulation for small businesses.