WatchGuard Dimension 2.3.2 fixes 15 vulnerabilities disclosed on November 19, 2026. All 15 affect Dimension 2.0 through versions earlier than 2.3.2, according to WatchGuard’s advisories. The flaws differ sharply in access needed and outcome, so the table below separates them before administrators plan the upgrade. For related product context, see Brandefense’s Vulnerability Intelligence platform.
The highest priority is CVE-2026-86130, a 9.3 CVSS 4.0 flaw that WatchGuard says permits unauthenticated remote code execution. The two other 9.3 flaws expose active administrator sessions to lower-privileged administrators. WatchGuard says it was unaware of exploitation in the wild when it published these advisories on November 19.
WatchGuard Dimension 2.3.2: All 15 CVEs Compared
Every row below has the same affected range and fix: Dimension 2.0 or later, before 2.3.2, is affected; 2.3.2 or later is listed as unaffected. Scores are WatchGuard’s CVSS 4.0 base scores. Its pages do not list CVSS 3.1 scores. The access column follows each individual advisory’s summary and required-configuration section.
| CVE | Access or condition | Consequence | CVSS 4.0 |
|---|---|---|---|
| CVE-2026-81430 | Authenticated administrator; management access | Arbitrary file creation or overwrite during upgrade | 8.6 High |
| CVE-2026-81434 | Device view permission; another user opens a crafted link | Script execution in that user’s browser | 4.8 Medium |
| CVE-2026-84322 | Low-privileged administrator; target session active | Management API exposes session IDs, enabling takeover | 9.3 Critical |
| CVE-2026-86094 | Low-privileged administrator; target session active | Diagnostic log exposes session token, enabling takeover | 9.3 Critical |
| CVE-2026-86126 | Unauthenticated attacker; Super Administrator visits malicious page | Persistent local Super Administrator account creation | 8.6 High |
| CVE-2026-86130 | Remote attacker; no authentication | Code execution as the Dimension WebUI process user | 9.3 Critical |
| CVE-2026-93911 | Enrolled device or valid device logging key | SQL injection leading to code execution | 8.7 High |
| CVE-2026-93912 | Enrolled device or valid device logging key | Log-notification code injection leading to code execution | 8.7 High |
| CVE-2026-93914 | Authenticated administrator; management access | Root commands during database snapshot restore | 8.6 High |
| CVE-2026-93915 | Low-privileged authenticated user; management access | Elevated OS commands through system settings | 7.7 High |
| CVE-2026-93916 | Holder of a valid Super Administrator session | Privileges persist after account downgrade or deletion | 8.6 High |
| CVE-2026-93917 | One enrolled device’s credentials; management access | Another device’s identity and queued configuration exposed | 8.6 High |
| CVE-2026-103579 | Authenticated administrator; management access | OS commands with local mail account privileges | 8.6 High |
| CVE-2026-103580 | Authenticated administrator; management access | Root commands during package update | 8.6 High |
| CVE-2026-126037 | Low-privileged authenticated user | Restricted device summary data disclosed | 5.3 Medium |
The table is an access and impact map, not a claim that every flaw can be exploited from the internet. Match the management interface, device enrollment, and user permissions in your environment to the relevant rows. For the common fix, compare the running build with WatchGuard’s 2.3.2 boundary.
Why the Three Critical Scores Describe Different Risks
CVE-2026-86130 starts in Dimension’s log collection service. WatchGuard describes missing authentication followed by SQL access and code execution under the WebUI process account. This is the only row the vendor describes as unauthenticated remote code execution. The remote code execution definition helps distinguish that outcome from account takeover.
CVE-2026-84322 and CVE-2026-86094 concern session identifiers instead. The first exposes active IDs through a management API response, while the second stores them in a diagnostic log. Both require a low-privileged Dimension Administrator and an active higher-privileged session, according to WatchGuard. They can enable Super Administrator session takeover without making the original access anonymous.
The diagnostic-log advisory calls CVE-2026-86094 a second unmitigated path for CVE-2026-78174. That cross-reference does not change this article’s fix boundary: WatchGuard lists Dimension 2.3.2 as the solution for CVE-2026-86094. Review old session handling separately if a prior mitigation was assumed to close all token exposure.
Which Administrator and Device Paths Matter After the Critical Flaws?
Several high-scoring flaws need administrator access, rather than an unauthenticated internet request. CVE-2026-93914 and CVE-2026-103580 can lead to root-level commands through restore or update functions. CVE-2026-103579 involves the outgoing mail configuration and the local mail-handling account. CVE-2026-81430 concerns arbitrary file writes during system upgrade, not a vendor claim of unauthenticated code execution.
Two log-processing flaws, CVE-2026-93911 and CVE-2026-93912, have a different trust boundary. WatchGuard’s summaries name an enrolled device or valid device logging key as the route to code execution. Their required-configuration sections also state that authenticated management access is needed. Preserve that wording when assessing exposure instead of treating these rows as anonymous access.
CVE-2026-93917 shows why device credentials belong in the same review. WatchGuard says control of one enrolled device’s credentials can let an attacker assume another device’s identity and receive its queued configuration. CVE-2026-93916 concerns a valid Super Administrator session that remains privileged after an account change. CVE-2026-93915 gives a low-privileged authenticated user an elevated command path.
The remaining flaws affect account creation, browser trust, and data access. CVE-2026-86126 needs a Super Administrator to visit an attacker-controlled page before a local administrator account can be created. CVE-2026-81434 requires device view permission and a victim opening a crafted link. CVE-2026-126037 lets a low-privileged user read restricted device summary data.
What Should Dimension Administrators Verify Now?
Inventory every Dimension instance and record its running version, not only its intended upgrade state. Prioritize reachable instances below 2.3.2, especially where log collection and management services are available to untrusted networks.
- Inventory each Dimension appliance and record its running version.
- Upgrade affected 2.0 through pre-2.3.2 installations to 2.3.2 or later.
- Confirm the running build and management access after the upgrade.
- Review administrator sessions, device credentials, and logs if exposure is suspected.
After upgrading, confirm the active build reports 2.3.2 or later and that expected device collection still works. If privileged-session or device-identity misuse is suspected, investigate relevant access records and rotate affected credentials using your normal response process. The patch management process provides context for recording build verification.
WatchGuard’s exploitation statement is a dated vendor assessment, not evidence that a particular deployment was safe. Its advisories published on November 19 say it was unaware of exploitation in the wild. This comparison uses those vendor pages for access conditions, outcomes, scores, and the fixed version; it does not infer victim counts or exploitation from severity.
Frequently Asked Questions
Which WatchGuard Dimension versions are affected?
WatchGuard lists Dimension 2.0 and later releases before 2.3.2 as affected across these 15 CVEs. It lists 2.3.2 or later as unaffected.
Are all 15 flaws unauthenticated remote code execution?
No. WatchGuard describes CVE-2026-86130 as unauthenticated remote code execution. Other flaws require administrator, user, device, or victim-session conditions and have different outcomes.
Does the vendor report active exploitation?
In advisories published November 19, 2026, WatchGuard says it was unaware of exploitation in the wild. That statement is the vendor’s dated assessment.
Sources
- WatchGuard PSIRT, Dimension advisories, November 19, 2026
- WatchGuard PSIRT, CVE-2026-86130, November 19, 2026
- WatchGuard PSIRT, CVE-2026-84322, November 19, 2026
- WatchGuard PSIRT, CVE-2026-86094, November 19, 2026
- WatchGuard PSIRT, CVE-2026-93911, November 19, 2026
- WatchGuard PSIRT, CVE-2026-93917, November 19, 2026
- WatchGuard PSIRT, CVE-2026-86126, November 19, 2026
- WatchGuard PSIRT, CVE-2026-103580, November 19, 2026
