WatchGuard Dimension 2.3.2 Fixes Code Execution and Account-Control Flaws

P1 — VALIDATE AND UPDATECritical maximum; individual ratings Medium to Critical · 9.3 maximum (CVSS v4.0)EXPLOITATION: NOT PUBLICLY REPORTED

Quick Answer

Upgrade affected Dimension appliances to 2.3.2, validate managed-device logging, and review unexpected administrative, session and device-identity activity.

Confirm Scope And Apply The Supported Remediation

What to do now: Inventory Dimension appliances, software versions, management and log-collection exposure, enrolled devices, logging keys and administrator roles. Separate the unauthenticated log-service issue from flaws requiring credentials, device keys, session tokens or a victim’s browser. The bundle does not imply all paths are unauthenticated. Install Dimension 2.3.2 through the supported appliance-update process. Maintain approved access restrictions while staging the update; restrictions are not a replacement for the fix. Confirm the running version, log ingestion and reporting; review administrative accounts, active sessions and managed-device registrations. Retain before-and-after versions and relevant logs.

Open the authoritative advisory

Last verified: 2026-11-20 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeWatchGuard Dimension 2.0 through versions before 2.3.2
AdvisoryCVE-2026-103579 / CVE-2026-103580 / CVE-2026-126037 / CVE-2026-81430 / CVE-2026-81434 / CVE-2026-84322 / CVE-2026-86094 / CVE-2026-86126 / CVE-2026-86130 / CVE-2026-93911 / CVE-2026-93912 / CVE-2026-93914 / CVE-2026-93915 / CVE-2026-93916 / CVE-2026-93917
CVEsCVE-2026-103579, CVE-2026-103580, CVE-2026-126037, CVE-2026-81430, CVE-2026-81434, CVE-2026-84322, CVE-2026-86094, CVE-2026-86126, CVE-2026-86130, CVE-2026-93911, CVE-2026-93912, CVE-2026-93914, CVE-2026-93915, CVE-2026-93916, CVE-2026-93917
Authoritative release date2026-11-19T18:28:39Z–18:28:40Z — individual vendor RSS publication times; group ordered by the final addition.
Authority revision dateNo separate material revision is stated for this release.
Affected versionsDimension >=2.0 and <2.3.2. Individual paths require unauthenticated log-service access, authenticated users or devices, valid session tokens, or user interaction as described by each advisory.
Fixed versionWatchGuard Dimension 2.3.2
CVSS base score9.3 maximum (CVSS v4.0)
CVSS severityCritical maximum; individual ratings Medium to Critical
Exploitation statusWatchGuard is not aware of exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

Fifteen Dimension advisories cover log-service code execution, session-token disclosure, device identity abuse, insufficient authorization and expiration, malicious upgrade/restore input, and browser attacks. CVE-2026-86130 allows unauthenticated log-service code execution; other paths have distinct prerequisites.

What To Validate Now

  1. Inventory. Inventory Dimension appliances, software versions, management and log-collection exposure, enrolled devices, logging keys and administrator roles.
  2. Establish applicability. Separate the unauthenticated log-service issue from flaws requiring credentials, device keys, session tokens or a victim’s browser. The bundle does not imply all paths are unauthenticated.
  3. Remediate. Install Dimension 2.3.2 through the supported appliance-update process. Maintain approved access restrictions while staging the update; restrictions are not a replacement for the fix.
  4. Validate. Confirm the running version, log ingestion and reporting; review administrative accounts, active sessions and managed-device registrations. Retain before-and-after versions and relevant logs.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Preserve logging continuity and recovery access during maintenance. Diagnostic logs can contain sensitive session identifiers; restrict access to retained evidence and do not test exploit paths against production.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.