Quick answers
- Is CVE-2026-78617 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78617 being exploited in the wild.
- How severe is CVE-2026-78617?
- Informational severity, with a CVSS score of 6.3, published 28 August 2026.
- Which products and versions are affected?
- Watchguard Dimension < 2.3.1.
- Is there a fix for CVE-2026-78617?
- A patch was published on 2026-08-27: Fixed in Dimension 2.3.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78617 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-78617?
- Check whether you run Watchguard Dimension 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.
Technical details
The vulnerability exists in WatchGuard Dimension's web login endpoint, which fails to implement rate-limiting or enforce account lockout on failed authentication attempts by default (CWE-307: Improper Restriction of Excessive Authentication Attempts). An unauthenticated remote attacker can exploit this over the network to conduct automated password-guessing attacks against user accounts. Although Dimension offers an optional account lockout mechanism that blocks further attempts after a configured threshold, this protection is not enabled by default, making it ineffective for organizations that do not explicitly configure it. The issue is resolved in Dimension 2.3.1 and later versions.
Affected products
- WatchGuard Dimension < 2.3.1
Timeline
- 2026-08-27: disclosed
- 2026-08-27: patched: Fixed in Dimension 2.3.1