Quick answers
- Is CVE-2026-93865 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93865 being exploited in the wild.
- How severe is CVE-2026-93865?
- Informational severity, published 27 October 2026.
- Which products and versions are affected?
- Watchguard Fireware OS Default >=2025.1 <2026.4, >=12.0 <12.12.4; T15/T35 >=12.0 <12.5.22.
- Is there a fix for CVE-2026-93865?
- Yes: fixed in Fireware OS 2026.4, Fireware OS 12.12.4, Fireware OS 12.5.22. Until then: This vulnerability only affects Firebox appliances configured as a member of a FireCluster; disabling the clustering feature or ensuring FireCluster is not enabled mitigates the risk. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93865 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-93865?
- Check whether you run Watchguard Fireware OS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Fireware OS 2026.4, Fireware OS 12.12.4, Fireware OS 12.5.22
This vulnerability only affects Firebox appliances configured as a member of a FireCluster; disabling the clustering feature or ensuring FireCluster is not enabled mitigates the risk.
Technical details
A missing authentication vulnerability (CWE-306, CWE-862) in the FireCluster synchronization daemon allows remote, unauthenticated command injection (CWE-77) when a Firebox appliance is configured as a FireCluster member. An attacker sending a specially crafted request to the FireCluster management IP can invoke administrative system-level actions with no authentication required, leading to remote code execution as root.
Affected products
- WatchGuard Fireware OS Default >=2025.1 <2026.4, >=12.0 <12.12.4; T15/T35 >=12.0 <12.5.22
Timeline
- 2026-10-27: disclosed