Skip to main content
Menu
CVEs

WatchGuard Dimension remote code execution in log collection service

Affects WatchGuard Dimension from version 2.0 up to but not including 2.3.2. Fixed in 2.3.2. No vendor severity rating is given, so the CVSS score of 9.3 (critical) is the only rating.

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

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 2.3.2
Who is exposed
Not reported

Summary

WatchGuard Dimension has a flaw in its log collection service that lets a remote attacker, without logging in, run arbitrary SQL statements and ultimately execute code as the Dimension WebUI process user. The attacker reaches it by sending specially crafted network requests.

Written by a model

Original description

A missing authentication vulnerability in WatchGuard Dimension's log collection service allows a remote, unauthenticated attacker to execute arbitrary SQL statements and ultimately execute arbitrary code as the Dimension WebUI process user by sending specially crafted network requests.

Who should check

Teams running WatchGuard Dimension 2.0 or later before 2.3.2, including any Dimension log collection service exposed to the network.

“Dimension >= 2.0, < 2.3.2”

psirt.watchguard.com

What to do

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-86130 (Dimension Improper Authentication in Log Collection Service Allows Unauthenticated 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-86130 (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 version 2.0 or later and before 2.3.2 (source: https://psirt.watchguard.com/CVE-2026-86130)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-86130 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-86130 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-86130
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-86130
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-86130"}.

Affected versions

cve.now Index

30Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • 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 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

Timeline

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

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

  4. Posted on X by cve.now
  5. Record last updated

Evidence 3

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

Questions about CVE-2026-86130

Is CVE-2026-86130 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?

The Dimension log collection service does not properly check authentication, so a remote attacker without credentials can reach it. The advisory says this lets an attacker run arbitrary SQL statements and ultimately arbitrary code as the Dimension WebUI process user.

Source: psirt.watchguard.com

Which versions are affected by CVE-2026-86130?

Dimension: from 2.0 before 2.3.2.

Source: cve.now feed data

Am I affected, and how do I check?

WatchGuard Dimension versions from 2.0 up to but not including 2.3.2 are affected. To check a installation, compare its Dimension version against that range.

Source: psirt.watchguard.com

How do I fix CVE-2026-86130?

Upgrade WatchGuard Dimension to 2.3.2 or later, the fixed version listed for this vulnerability.

Source: psirt.watchguard.com

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