WatchGuard says crafted network requests can let a remote, unauthenticated attacker execute arbitrary SQL statements and ultimately run code as the Dimension WebUI process user. The vendor published the advisory on 19 November 2026.The affected component is Dimension's log collection service, not every WatchGuard product. The risk depends on whether an affected Dimension instance and that service are reachable to an attacker. WatchGuard assigns the flaw CVSS 4.0 9.3 Critical; neither its advisory nor the CNA record supplies a CVSS 3.1 score.
What it allows
How Does CVE-2026-86130 Reach Code Execution?
The missing control is authentication at Dimension's log collection service. WatchGuard says a remote attacker can send crafted network requests without signing in. The requests can lead to arbitrary SQL statements and then arbitrary code execution under the Dimension WebUI process user.
WatchGuard also lists CWE-441 and CWE-502 among the weakness categories. Its public summary does not explain the exact intermediate sequence from SQL execution to code execution. For related product context, see Brandefense's Vulnerability Intelligence platform.
On 19 November 2026, WatchGuard said it was not aware of exploitation of this vulnerability in the wild. That statement describes only what the vendor knew at publication. We recommend treating reachable, affected instances as urgent because the described path needs no account.
Who is affected
Which CVE-2026-86130 Versions Need Action?
WatchGuard lists Dimension 2.0 and later releases before 2.3.2 as affected. The advisory marks Dimension 2.3.2 and later as not affected and names 2.3.2 as the solution. Check the installed Dimension version on each deployment rather than relying on the planned upgrade version.
For exposure triage, record which networks can reach the log collection service. A management interface being restricted does not, by itself, establish that the log collection service is unreachable. Use the vulnerability prioritization guide to weigh confirmed reachability and the installed version.
Apply Dimension 2.3.2 or a later release approved by WatchGuard, then confirm the running version after maintenance. Keep the installed build and maintenance record in the patch management process. If maintenance must wait, restrict access to the affected service to required trusted systems as a temporary defensive measure.
Timeline
- 2026-11-19
WatchGuard published the CVE advisory and named Dimension 2.3.2 as the solution.
What to do
-
Inventory Dimension deployments
Record the installed Dimension version and the networks that can reach its log collection service. Prioritize instances from 2.0 to before 2.3.2 that are reachable from untrusted networks.
-
Upgrade affected instances
Install WatchGuard Dimension 2.3.2 or a later vendor-approved release on affected deployments. Follow the vendor's normal maintenance process for each instance.
-
Verify the running version
After maintenance, check that each Dimension instance is running 2.3.2 or later. Record the observed version and confirm required log collection still works.
-
Review available activity records
Review network, application and host records for unexpected access to the log collection service or unusual WebUI-process activity. This is our triage suggestion, not a vendor-published detection signature.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-86130 in Brandefense Atlas
The Atlas record of CVE-2026-86130: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-86130 require a Dimension account?
No. WatchGuard describes a remote, unauthenticated path through Dimension's log collection service. The stated result is code execution as the Dimension WebUI process user.
Which Dimension versions are affected?
WatchGuard lists Dimension 2.0 through releases before 2.3.2 as affected. It marks 2.3.2 and later as not affected.
Which release fixes CVE-2026-86130?
WatchGuard names Dimension 2.3.2 as the solution. After upgrading, verify that the instance is actually running 2.3.2 or later.
Has WatchGuard reported exploitation in the wild?
In its 19 November 2026 advisory, WatchGuard said it was not aware of exploitation in the wild. That statement is limited to the vendor's awareness at publication.
Sources
- CVE-2026-86130 WatchGuard PSIRT AdvisoryWatchGuard
- CVE-2026-86130 RecordWatchGuard CNA via CVE Program