When the Firewall Opens the Door: Check Point Under Attack and SonicWall MFA at Risk
Check Point confirms destructive attacks, while SonicWall fixes an exploited flaw that bypasses SAML/MFA. What OT teams should review this week.

Editorial
This week, we are not dealing with vulnerabilities that can wait for the next monthly patch cycle. Check Point confirmed a campaign targeting unpatched Security Gateways: attackers entered through the Mobile Access portal, escalated privileges to root, installed backdoors and, in some cases, moved into VMware ESXi to deploy a data wiper. SonicWall, meanwhile, fixed an actively exploited SSL-VPN vulnerability that can bypass SAML controls and the MFA tied to them.
We are concerned by the speed at which newly disclosed vulnerabilities turn into real intrusions. We are equally concerned that these attacks are becoming increasingly destructive. In OT security, the word “lethal” should not be used as a marketing device: wiping a server does not, by itself, amount to physical harm. However, when the compromised equipment protects or connects energy, manufacturing, water or building processes, the loss of visibility and control can create unsafe conditions with serious consequences for people and operations. That possibility requires us to treat the perimeter as part of the plant’s safety system, not merely as IT infrastructure.
The priority for this edition is straightforward: identify exposed gateways, confirm their versions, apply vendor fixes and search for evidence of compromise. Updating without reviewing historical evidence may leave an active backdoor behind an appliance that is now fully patched.
Beyond raising awareness among our readers, we want to emphasize how quickly new vulnerabilities are identified and then begin to be exploited. This reality should lead us to review—and, where necessary, rethink—our cybersecurity strategy so that it can address the new challenges posed by artificial intelligence, both in its ability to accelerate attacks and in the opportunities it offers to strengthen defense.
Check Point: PHP2Shell was used to gain entry, escalate to root and wipe systems
Check Point Research confirmed exploitation activity against unpatched Security Gateways with an exposed Mobile Access portal. The chain began with PHP2Shell—CVE-2026-109618 and CVE-2026-109619— to obtain initial access. The attackers then exploited CVE-2026-123039, a local vulnerability in the DynamicCLI interface, to escalate privileges to root.
The incident did not end at the gateway. The attackers installed web shells, deployed the TSGA and TSProxy backdoors, conducted internal network reconnaissance and, in some cases, moved over SSH to a VMware ESXi host. There, they ran a wiper identified as destroy_v6. Check Point observed a first wave on October 30 and a second on November 2 that expanded the activity to organizations across multiple countries and sectors.
The lesson for OT is direct: a compromised security gateway is not simply “a firewall that went down.” It is a privileged vantage point from which to observe connections, capture configurations, conceal traffic and pivot toward internal assets. If that gateway controls access for vendors, engineers or operations centers, it must be considered a potential route into the industrial network.
What to do:
- Confirm whether any Check Point Security Gateways have Mobile Access enabled and exposed to the internet.
- Install the Check Point fixes for PHP2Shell and CVE-2026-123039; do not attempt to address the issue by updating PHP independently.
- Search for activity involving the addresses published by the vendor,
zz*.tplfiles, processes or files related toCPconfigdaemon,slot_CPconfigdaemonandlibcpfwcommon.so, as well as unusual PHP or Apache events. - Review SSH connections initiated from the gateway toward ESXi or other internal servers, together with changes to configurations, backups and logs.
- If indicators are found, isolate the appliance and activate the incident-response process. A patch does not remove web shells, persistence mechanisms or stolen credentials.
Read the investigation and indicators published by Check Point
SonicWall: an exploited flaw can bypass SAML and SSL-VPN MFA
Advisory SNWLID-2026-0014 covers seven vulnerabilities in SonicOS for Gen 7 and Gen 8 firewalls. The most urgent is CVE-2026-19868, an authentication-enforcement flaw in the SSL-VPN service. In SAML deployments, an attacker who already possesses valid credentials for an alternative authentication method may bypass SAML authentication and the MFA it enforces. SonicWall investigated activity consistent with exploitation, and CISA added the vulnerability to its Known Exploited Vulnerabilities catalog.
The requirement for valid credentials does not make this a theoretical risk. Stolen or reused passwords—and credentials belonging to third parties—are among the most common paths into remote-access services. If an organization relies on SAML MFA to stop that abuse, this vulnerability removes one of its primary barriers.
Affected releases include SonicOS 7.3.3-7015 and earlier on Gen 7, and SonicOS 8.2.2-8015 and earlier on Gen 8. Fixes are available in 7.3.4-7013 or later for Gen 7 and 8.2.3-8015 or later for Gen 8. The advisory also addresses other high- and medium-severity issues, so teams should review the complete set rather than focusing solely on CVE-2026-19868.
What to do:
- Identify Gen 7 and Gen 8 SonicWall firewalls that expose SSL-VPN, particularly those using SAML.
- Upgrade to the fixed release appropriate for the model, and retain a validated configuration backup before making the change.
- Review successful SSL-VPN access through alternative methods, logins that do not show the expected SAML/MFA flow, unusual hours and third-party accounts.
- Invalidate active sessions and rotate credentials when there is evidence of misuse; do not assume the update terminates sessions obtained before patching.
- Limit the reach of VPN accounts and prevent remote sessions from accessing OT assets directly without a controlled and monitored jump point.
Read the official SonicWall advisory
Siemens: PHP2Shell and Node2Shell reach industrial products
The Siemens advisories confirm a second pattern that should not be lost amid the perimeter attacks: vulnerabilities in general-purpose components are reaching OT inside industrial products. PHP2Shell affects multiple building-automation and energy product lines. Node2Shell—CVE-2026-111497—, an out-of-bounds write in the Brotli decoder bundled with Node.js, appears in Industrial Edge Management, Desigo, Gridscale and RUGGEDCOM APE1808.
Not every product and configuration has the same exposure. For Industrial Edge Management, for example, Siemens states that an installation without Management Applications does not use or expose the affected functionality. Where Management Applications or Device Applications are present, the specific fixes or mitigations must be applied. For Desigo CC V8 and V9, Gridscale and other products, the exact version determines the appropriate action.
What to do:
- Do not search only for “PHP” or “Node.js” in a scan. Cross-reference the product inventory, version and installed applications against the Siemens matrices.
- Prioritize systems exposed to the corporate network, a DMZ, remote access or the internet.
- In Industrial Edge Management, confirm whether Management Applications or Device Applications are installed before deciding on the intervention.
- Use only Siemens-validated releases and mitigations; updating the runtime independently may affect support and operations.
Review PHP2Shell in Siemens products Review Node2Shell in Siemens products
In brief
- Circutor PowerStudio SCADA WAVE: INCIBE-CERT reported improper digital-signature verification. Confirm the version and obtain the fix through Circutor or its integrator; in the meantime, restrict administration to controlled network segments.
- ABB OPTIMAX: a use-after-free vulnerability may lead to instability, data corruption or code execution. Review the version, exposure and available patch with ABB before modifying a production optimization platform.
- Helmholz and MB connect line: recent advisories affect equipment used for industrial remote access. If these devices form part of the vendor-support path, treat them with the same priority as a corporate VPN.
- Welotec egOS and DURAG D-ESI 100: new advisories reinforce the need to include industrial routers and emissions-monitoring systems in the OT vulnerability inventory.
Read the Circutor advisory from INCIBE-CERT Read the ABB OPTIMAX advisory from INCIBE-CERT
Closing thoughts
This edition leaves us with an uncomfortable warning: the devices we deploy to protect access also concentrate credentials, trust and visibility across the network. That makes them high-value targets. Check Point demonstrates how an intrusion through the gateway can lead to persistence, lateral movement and destruction. SonicWall reminds us that MFA cannot serve as the final barrier when an authentication path can bypass it.
The response cannot stop at “install the patch.” Teams must confirm exposure, review earlier access, search for persistence, reduce privileges and separate remote access from industrial assets. In OT, losing the perimeter can affect far more than confidentiality: it may undermine availability, operational visibility and, in the worst case, people’s safety.
Share this edition with the teams responsible for firewalls, VPNs, virtualization, vendor access and industrial networks. This week’s question is simple: if the gateway is compromised today, how far can the attacker go?
Until next week.
Roberto Manzo
The analysis and prioritization expressed in Perímetro are the editorial responsibility of Roberto Manzo. This newsletter does not replace vendor instructions or a technical assessment specific to your organization.
