WatchGuard Dimension remote code execution in log notification processing
Affects WatchGuard Dimension versions 2.0 up to but not including 2.3.2, for attackers holding an authenticated managed device or a valid device logging key. Fixed in 2.3.2.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.3.2
- Who is exposed
- Specific setups only
Summary
A code injection flaw in WatchGuard Dimension's log notification processing lets a remote attacker with low-level access run arbitrary code on the Dimension appliance. The attacker must be an authenticated managed device or hold a valid device logging key, and no user action is needed.
Written by a model
Original description
A code injection vulnerability in WatchGuard Dimension's log notification processing allows an authenticated managed device, or an attacker in possession of a valid device logging key, to achieve arbitrary code execution on the Dimension appliance.
Who should check
Teams running WatchGuard Dimension versions 2.0 through 2.3.1, or anyone with managed devices reporting logs to Dimension.
“Dimension >= 2.0, < 2.3.2”
What to do
Check whether your setup matches what the bug needs.
WatchGuard Dimension versions >= 2.0 and < 2.3.2 are affected. Attacker needs an authenticated managed device or a valid device logging key. Exploit requires authenticated network access to the Dimension management interface.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-93912 (Dimension Code Injection in Log Notification Processing Allows Remote Code Execution), 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-93912 (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 and < 2.3.2 are affected. (source: https://psirt.watchguard.com/CVE-2026-93912)
- Attacker needs an authenticated managed device or a valid device logging key. (source: https://psirt.watchguard.com/CVE-2026-93912)
- Exploit requires authenticated network access to the Dimension management interface. (source: https://psirt.watchguard.com/CVE-2026-93912)
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-93912 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-93912 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-93912
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-93912
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-93912"}.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
- Severity9.7/10CVSS 8.7, 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
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | psirt.watchguard.com · CVE-2026-93912 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-93912 |
| Record | NVD · CVE-2026-93912 |
Questions about CVE-2026-93912
Is CVE-2026-93912 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?
Malicious code can be injected through the log notification processing in WatchGuard Dimension. The injected code can run on the Dimension appliance.
Source: psirt.watchguard.com
Which versions are affected by CVE-2026-93912?
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 or later and before 2.3.2 are affected. The attacker needs either an authenticated managed device or a valid device logging key, plus authenticated network access to the Dimension management interface. Check the installed Dimension version against that range.
Source: psirt.watchguard.com
How do I fix CVE-2026-93912?
Upgrade WatchGuard Dimension to version 2.3.2 or later.
Source: psirt.watchguard.com
Related
- CVE-2026-86130Dimension Improper Authentication in Log Collection Service Allows Unauthenticated Remote Code Execution
- CVE-2026-86094Dimension Session Hijack via Exposed Session Tokens in Diagnostic Logs
- CVE-2026-84322Dimension Session Hijack via Exposed Session Tokens in Management API
- 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.