WatchGuard Dimension session token leak in web UI diagnostic logs
Affects WatchGuard Dimension 2.0 up to but not including 2.3.2, where a Super Administrator's session identifier can land in diagnostic logs. Fixed in 2.3.2.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.3.2
- Who is exposed
- Specific setups only
Summary
WatchGuard Dimension writes unredacted session identifiers for logged-in users into its web UI diagnostic log. A remote attacker who holds a low-privileged Dimension Administrator account can read that log, take a Super Administrator's session token while that administrator is logged in, and take over the account.
Written by a model
Original description
WatchGuard Dimension records unredacted session identifiers for logged-in users in its web UI diagnostic log. A low-privileged Dimension Administrator can retrieve this log and extract a Super Administrator's session token while that administrator is logged in, enabling account takeover.
This vulnerability is a secondary unmitigated attack path for CVE-2026-78174.
Who should check
Teams running WatchGuard Dimension 2.0 through 2.3.1 where low-privileged Dimension Administrators have network access to the management interface.
“Dimension >= 2.0, < 2.3.2”
What to do
Check whether your setup matches what the bug needs.
Affected product is WatchGuard Dimension versions 2.0 up to but not including 2.3.2. Attacker needs authenticated network access to the Dimension management interface. A Super Administrator must be logged in while the diagnostic log holds their session identifier.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-86094 (Dimension Session Hijack via Exposed Session Tokens in Diagnostic Logs), 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-86094 (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):
- Affected product is WatchGuard Dimension versions 2.0 up to but not including 2.3.2. (source: https://psirt.watchguard.com/CVE-2026-86094)
- Attacker needs authenticated network access to the Dimension management interface. (source: https://psirt.watchguard.com/CVE-2026-86094)
- A Super Administrator must be logged in while the diagnostic log holds their session identifier. (source: https://psirt.watchguard.com/CVE-2026-86094)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-86094 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-86094 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-86094
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-86094
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-86094"}.Affected versions
- WatchGuard DimensionFrom 2.0 · fixed in 2.3.2
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, 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
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Posted on X by cve.now
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | psirt.watchguard.com · CVE-2026-86094 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-86094 |
| Record | NVD · CVE-2026-86094 |
Questions about CVE-2026-86094
Is CVE-2026-86094 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?
A low-privileged Dimension Administrator can extract a Super Administrator's session token from the diagnostic log while that administrator is logged in. With that token, the attacker can take over the Super Administrator's account.
Source: psirt.watchguard.com
Which versions are affected by CVE-2026-86094?
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 in the affected range. The exposure also requires a Super Administrator to be logged in while the diagnostic log holds their session identifier, and an attacker needs authenticated network access to the Dimension management interface. Compare your installed Dimension version against that range.
Source: psirt.watchguard.com
How do I fix CVE-2026-86094?
Upgrade Dimension to version 2.3.2 or later, which is the fixed version.
Source: psirt.watchguard.com
Related
- CVE-2026-86130Dimension Improper Authentication in Log Collection Service Allows Unauthenticated Remote Code Execution
- CVE-2026-84322Dimension Session Hijack via Exposed Session Tokens in Management API
- CVE-2026-93912Dimension Code Injection in Log Notification Processing Allows Remote Code Execution
- CVE-2026-93911Dimension SQL Injection in Log Collector Allows Remote Code Execution
- CVE-2026-103580Dimension OS Command Injection in Package Update Allows Remote Code Execution as Root
- CVE-2026-103579Dimension CRLF Injection in Email Server Configuration Allows Remote Code Execution
No corrections so far. Something wrong on this page? Report an error.