WatchGuard Dimension's web login endpoint does not enforce effective rate-limiting or account lockout by default allowing a remote attacker to perform automated password guessing against user accounts. If the account lockout setting is enabled, brute-force attempts are blocked after a defined number of failed attempts, but this setting is not enabled by default.
CVE-2026-78617
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(medium)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026CVE-2026-78617 — WatchGuard Dimension Web UI Authentication Brute-Force Due to Missing Rate Limiting
https://psirt.watchguard.com/CVE-2026-78617Vendor Advisories for CVE-2026-78617(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 22:20 UTCEG score recompute
- 2026-08-29 22:20 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 20:37 UTCGHSA enrichment
- 2026-08-28 18:58 UTCGHSA enrichment
- 2026-08-28 02:18 UTCEG score recompute
- 2026-08-28 02:10 UTCEG score recompute
- 2026-08-28 02:07 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-307 · CWE-203
- CVE-2013-10004NVD 6.5EG 9.8CRITICAL
- CVE-2013-4441EG 9.8CRITICAL
- CVE-2018-19879NVD 7.1EG 9.8CRITICAL
- CVE-2018-1000884EG 9.8CRITICAL
- CVE-2018-19548EG 9.8CRITICAL
- CVE-2018-15759NVD 9.1EG 9.8CRITICAL
- CVE-2018-11082NVD 6.6EG 9.8CRITICAL
- CVE-2018-12993EG 9.8CRITICAL
- CVE-2018-12649EG 9.8CRITICAL
- CVE-2018-1475EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-78617?
When was CVE-2026-78617 disclosed?
Is CVE-2026-78617 actively exploited?
What is the CVSS score of CVE-2026-78617?
How do I remediate CVE-2026-78617?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78617
Is Your Infrastructure Affected by CVE-2026-78617?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.