Quick answers
- Is CVE-2026-104381 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104381 being exploited in the wild.
- How severe is CVE-2026-104381?
- Informational severity, published 27 October 2026.
- Which products and versions are affected?
- Watchguard Fireware OS 12.0 before 12.5.22; 12.0 before 12.12.4; 2025.1 before 2026.4.
- Is there a fix for CVE-2026-104381?
- Yes: fixed in Fireware OS 2026.4, Fireware OS 12.12.4, Fireware OS 12.5.22. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104381 attacked?
- It is attacked from the adjacent network, in a network appliance.
- Am I affected by CVE-2026-104381?
- 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
Technical details
A missing authentication vulnerability (CWE-306, CWE-294) in Fireware OS's FireCluster state synchronization feature allows an unauthenticated attacker positioned on the cluster synchronization network segment to send crafted synchronization traffic that terminates BOVPN tunnels prematurely. The vulnerability requires the attacker to be on the cluster network and the appliance to be deployed as a FireCluster with at least one BOVPN tunnel configured; no patch has been released as of the advisory date.
Affected products
- WatchGuard Fireware OS 12.0 before 12.5.22; 12.0 before 12.12.4; 2025.1 before 2026.4
Timeline
- 2026-10-27: disclosed