FireCluster root action invocation
A cluster-interconnect attacker, including a compromised peer or on-path attacker, can invoke privileged management actions on a FireCluster member.
WatchGuard’s October 27 Fireware batch includes cluster root-action injection, SIP proxy RCE, AD-response overflows and configuration leaks. Preconditions differ; the vendor reports no known exploitation. Update to the model-appropriate fixed release.
L3 reflects multiple security-boundary failures in mainstream edge appliances. This is not a universal unauthenticated Internet-to-root chain: AD, cluster interconnect, FIPS logging, local access and cloud interception are distinct prerequisites. The SSH configuration-read, SIP proxy and enabled FireCluster management-IP issues deserve their own exposure checks. No victim count is established. The same date’s Mobile VPN Windows-client issue is a different product and is not included in this 17-flaw count.
A cluster-interconnect attacker, including a compromised peer or on-path attacker, can invoke privileged management actions on a FireCluster member.
An attacker on the cluster interconnect can repeatedly crash synchronization on a FireCluster deployment.
An authenticated Device Monitor or higher role with CLI access can write numeric content to arbitrary paths or kernel parameters as root.
Requires AD authentication configuration and control/interception of configured AD-server traffic; a crafted response can crash the service or execute code.
Requires AD authentication configuration and control/interception of configured AD-server traffic; a crafted response can crash the service or execute code.
An unauthenticated caller reaching management SSH can extract configuration secrets.
An authenticated Mobile VPN user can crash or execute code as an unprivileged process when Network Access Control is enabled.
An authenticated attacker with management-interface access can crash certd and potentially execute code.
Requires local appliance access, AuthPoint integration and persuading a victim to accept an MFA push; not an unauthenticated Internet MFA bypass.
Requires a FireCloud Gateway and TLS-decrypted man-in-the-middle access between it and WatchGuard Cloud; altered WireGuard configuration may cause DoS or code execution.
An attacker on the cluster synchronization segment can prematurely terminate tunnels when FireCluster and at least one BOVPN tunnel are configured.
An unauthenticated network caller reaching the FireCluster management IP can invoke privileged administrative actions when clustering is enabled.
Requires FIPS mode, an external log server and an adjacent attacker able to impersonate/intercept that server; a crafted certificate can execute code as root.
An unauthenticated request through a policy using the configured SIP proxy can execute code.
An unauthenticated caller reaching management can repeatedly crash its service and interrupt administrator sessions; traffic processing is unaffected.
An unauthenticated caller can cause a heap out-of-bounds write through WebSocket handling when Access Portal is enabled.
A local low-privilege process can plant a filesystem object and trigger a list update to overwrite files as root; content is partly constrained.
| Product | Safe from | Note |
|---|---|---|
| Fireware newer release family | 2026.4 | |
| Fireware 12.x standard platforms | 12.12.4 | |
| Fireware T15/T35 | 12.5.22 |
Oct 27, 2026
WatchGuard publishes the 17 Fireware advisories
We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.