Skip to main content
Menu
CVEs

WatchGuard Dimension remote code execution in system settings endpoint

Affects WatchGuard Dimension 2.0 up to but not including 2.3.2, where a low-privileged authenticated user with network access to the management interface can run commands with elevated OS privileges. Fixed in 2.3.2.

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

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

Summary

Affected is WatchGuard Dimension. A low-privileged user with a login on the network can run arbitrary commands on the underlying operating system with elevated privileges, by reaching a settings handler that lacks an authorization check.

Written by a model

Original description

A missing authorization vulnerability in WatchGuard Dimension's legacy system settings configuration handler allows a low-privileged authenticated user to execute arbitrary commands with elevated privileges on the underlying OS.

Who should check

Teams running WatchGuard Dimension versions 2.0 through 2.3.1 that expose the management interface to authenticated network users.

“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 has authenticated network access to the Dimension management interface.
  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-93915 (Dimension Missing Authorization in System Settings Endpoint 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-93915 (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-93915)
- Attacker has authenticated network access to the Dimension management interface. (source: https://psirt.watchguard.com/CVE-2026-93915)
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-93915 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-93915 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-93915
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-93915
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-93915"}.

Affected versions

cve.now Index

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

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 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-93915
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-93915
RecordNVD · CVE-2026-93915

Questions about CVE-2026-93915

Is CVE-2026-93915 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 missing authorization check in a system settings endpoint lets a low-privileged authenticated user run arbitrary commands with elevated privileges on the underlying operating system.

Source: psirt.watchguard.com

Which versions are affected by CVE-2026-93915?

Dimension: from 2.0 before 2.3.2.

Source: cve.now feed data

Am I affected, and how do I check?

The range is Dimension versions 2.0 up to but not including 2.3.2, and the issue requires authenticated network access to the Dimension management interface. Compare the installed Dimension version against that range to check a given system.

Source: psirt.watchguard.com

How do I fix CVE-2026-93915?

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

Source: psirt.watchguard.com

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