Skip to main content
Menu
CVEs

WatchGuard Dimension persistent admin access via unexpired WebUI sessions

Affects WatchGuard Dimension 2.0 up to but not including 2.3.2, where an attacker holding a valid Super Administrator WebUI session keeps that access after the account is downgraded or deleted. Fixed in 2.3.2.

CVE-2026-93916Published November 19, 2026, updated

8.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.3.2
Who is exposed
Specific setups only

Summary

WatchGuard Dimension does not expire administrator sessions properly, so an attacker who can reach it over the network and already holds a valid Super Administrator WebUI session can keep full Super Administrator privileges after another administrator downgrades or deletes that account. Exploiting it requires an existing high-privilege login, and no user action is needed.

Written by a model

Original description

An insufficient session expiration vulnerability in WatchGuard Dimension's administrator session management allows an attacker holding a valid Super Administrator WebUI session to retain full Super Administrator privileges after that account has been downgraded or deleted by another administrator.

Who should check

Teams running WatchGuard Dimension versions 2.0 through 2.3.1 and anyone who manages Super Administrator accounts in Dimension.

“Dimension >= 2.0, < 2.3.2”

psirt.watchguard.com

What to do

  1. Check whether your setup matches what the bug needs.

    WatchGuard Dimension versions 2.0 up to but not including 2.3.2. Attacker must hold a valid Super Administrator WebUI session.
  2. Upgrade to a fixed version: 2.3.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-93916 (Dimension Insufficient Session Expiration Allows Persistent Super Administrator Access), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-93916 (entry last updated 2026-11-19):
Affected:
- WatchGuard Dimension: from 2.0, fixed in 2.3.2
Fixed versions: 2.3.2.
Conditions (all must be true for the bug to be hit):
- WatchGuard Dimension versions 2.0 up to but not including 2.3.2. (source: https://psirt.watchguard.com/CVE-2026-93916)
- Attacker must hold a valid Super Administrator WebUI session. (source: https://psirt.watchguard.com/CVE-2026-93916)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-93916 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-93916 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://psirt.watchguard.com/CVE-2026-93916
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-93916
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-93916"}.

Affected versions

cve.now Index

18Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.6/10CVSS 8.6, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorypsirt.watchguard.com · CVE-2026-93916
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-93916
RecordNVD · CVE-2026-93916

Questions about CVE-2026-93916

Is CVE-2026-93916 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Sessions in WatchGuard Dimension do not expire properly, so a Super Administrator session can keep full privileges even after another administrator has downgraded or deleted that account. The attacker must already hold a valid Super Administrator WebUI session.

Source: psirt.watchguard.com

Which versions are affected by CVE-2026-93916?

Dimension: from 2.0 before 2.3.2.

Source: cve.now feed data

Am I affected, and how do I check?

WatchGuard Dimension versions 2.0 up to but not including 2.3.2 are affected. To check, look at the Dimension version shown in the WebUI or on the appliance, and compare it with 2.3.2.

Source: psirt.watchguard.com

How do I fix CVE-2026-93916?

Upgrade WatchGuard Dimension to version 2.3.2, which is the fixed version listed for this vulnerability.

Source: psirt.watchguard.com

No corrections so far. Something wrong on this page? Report an error.