Control Validation for CVE-2026-93865 in WatchGuard Environments
An upgrade record can show that a package was installed. It does not prove that a firewall re-entered service with the intended configuration or that only approved networks can reach its cluster-management interface. CVE-2026-93865 gives security teams a reason to validate both the firmware state and the network controls around FireCluster.
Vulnerability overview
WatchGuard assigned CVE-2026-93865 a CVSS v4.0 score of 9.2. The Fireware OS FireCluster synchronization daemon has a missing authentication vulnerability. A remote attacker can use a crafted request to the cluster management IP to invoke privileged system-level administrative actions when clustering is enabled.
The vendor maps the defect to CWE-77, CWE-306 and CWE-862. WatchGuard says it was not aware of in-the-wild exploitation when the advisory was published.
Mechanism and exploitation conditions
The vulnerable path is reachable over the network and does not require an authenticated session in the condition described by the advisory. FireCluster must be enabled. The public advisory does not provide a request trace or a list of commands that can be issued.
Validation should therefore test reachability and patch state, not attempt to reproduce an exploit. Ask which routes can reach the management IP, which hosts use those routes and whether access is limited to a documented administrative path.
Impact
The CVSS vector records high confidentiality, integrity and availability impact to the vulnerable system. A firewall change can affect the protected network, so device-level success can create enterprise-level consequences. The public record does not assert that exploitation is known to be occurring.
Affected products and scope
Affected default Fireware OS versions are 2025.1 through releases before 2026.4 and 12.0 through releases before 12.12.4. T15 and T35 appliances are affected from 12.0 through releases before 12.5.22. The vendor's configuration condition is FireCluster membership.
The test scope should include management routes, VPN policy, administrative jump hosts, monitoring paths and the cluster's standby member. A console that shows the primary member in a healthy state may not prove that every route and appliance is correctly controlled.
Exposure context
ZoomEye returned 44,604 matches for app="WatchGuard Firebox" and 0 for the exact CVE. The product count provides a broad external surface signal. It does not prove vulnerable firmware or cluster exposure. The CVE count is a limited index result and should be reported with that limitation.
Remediation and mitigations
Patch each affected cluster member to Fireware OS 2026.4 or later, 12.12.4 or later, or 12.5.22 or later for T15 and T35. Verify the running image, cluster membership and configuration after the change.
The advisory does not offer a software workaround. As an interim control, restrict access to the cluster management IP to trusted networks and remove unnecessary management exposure. Record the expected allowlist, test it from an unapproved network and repeat the test after patching.
Completion should include device evidence, such as the running version, cluster status, active management rules and the date of the last configuration review.
Top comments (0)