Is your WatchGuard Dimension open to CVE-2026-86130?
WatchGuard published CVE-2026-86130 on 19 November 2026 and rates it CVSS 4.0 9.3 Critical. Missing authentication in the Dimension log collection service lets a remote attacker with no credentials run arbitrary SQL and then run code as the Dimension WebUI process user. Dimension 2.0 up to but not including 2.3.2 is affected. Upgrade to Dimension 2.3.2 now. The same release fixes 14 more Dimension flaws.
Critical (CVSS 4.0 9.3, WatchGuard). Published 19 November 2026
WatchGuard published the advisory on 19 November 2026 and NVD published CVE-2026-86130 at 19:17 GMT the same day. No exploitation reported as of 19 November 2026: WatchGuard says it is not aware of any exploitation in the wild. The identifier was not in CISA KEV when we checked at 20:59 GMT on 19 November 2026 (catalogue 2026.11.18). Absence from that catalogue does not prove there has been no exploitation.
By Simon Phillips, CTO. Reviewed by Oliver Legg, Head of SOC and IR. Last updated 19 November 2026, 20:59 GMT.
At a Glance
Based on WatchGuard's PSIRT advisories for CVE-2026-86130 and the 14 related Dimension CVEs, the NVD record published at 19:17 GMT on 19 November 2026, and a CISA KEV check at 20:59 GMT on 19 November 2026. Last updated 19 November 2026, 20:59 GMT.
Critical (CVSS 4.0 9.3, WatchGuard)
Vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N, scored by WatchGuard and shown in the NVD record. Network reachable, no privileges and no user interaction required.
Fix available: Dimension 2.3.2
WatchGuard lists Dimension 2.3.2 as the solution for CVE-2026-86130 and all 14 related Dimension advisories published the same day. No workaround is listed.
Dimension 2.0 up to 2.3.2
Every Dimension release from 2.0 up to but not including 2.3.2. Dimension is the on-premises log and reporting VM for Firebox fleets, often run by MSPs for many clients.
None reported
No exploitation reported as of 19 November 2026. WatchGuard is not aware of any exploitation in the wild. Not in CISA KEV (catalogue 2026.11.18, checked 20:59 GMT).
WatchGuard publishes CVE-2026-78174, a Dimension session token exposure in diagnostic logs, fixed in Dimension 2.3.1.
WatchGuard publishes CVE-2026-86130 and 14 more Dimension advisories, all fixed in Dimension 2.3.2. One of them, CVE-2026-86094, is a further path for CVE-2026-78174.
NVD publishes CVE-2026-86130 with WatchGuard's CVSS 4.0 9.3 score and the affected range 2.0 up to 2.3.2.
CybaVerse checks CISA KEV (catalogue 2026.11.18). None of the 15 Dimension CVEs are listed.
What to Do in the Next 24 Hours
Vendor advice and our advice are labelled separately. Tick both tracks.
Upgrade every Dimension VM to 2.3.2
- Upgrade WatchGuard Dimension to 2.3.2. WatchGuard lists 2.3.2 and later as not affected.
- Upgrade path (WatchGuard 2.3.2 release notes): from 2.3 or higher, apply the 2.3.2 upgrade file. Below 2.3, deploy a new 2.3 or higher instance, run its Setup Wizard, then migrate your database to it. WatchGuard says to set the same Log Server Authentication Key as on the old instance. From 2.1.2 Update 3 or lower, install 2.1.2 Update 4 first, because database migration needs it. Take a VM snapshot before you start.
- 2.3.2 is the listed solution for CVE-2026-86130 and for the 14 other Dimension advisories published on 19 November 2026, including the Critical session token flaws CVE-2026-84322 and CVE-2026-86094.
- The advisories do not list a workaround. If you patched CVE-2026-78174 by moving to 2.3.1 in August, you still need 2.3.2.
Patch first, lock down access, then hunt
- Treat this as an emergency change. Patch any Dimension VM reachable from the internet first, then MSP-managed client instances.
- Keep the Dimension web UI and log collection ports off the internet, reachable only from managed Fireboxes and your admin VLAN. This reduces exposure. It is not a vendor workaround and does not replace the update.
- Review Dimension administrator accounts and remove low-privileged administrators you do not need. Several of the related flaws start from a low-privileged Dimension Administrator.
- Hunt for the signs in the Reactive section below. If you suspect compromise, isolate the VM, rotate Dimension and Firebox management credentials, and rebuild from a clean 2.3.2 image.
Proactive: Find Exposure and Patch
Vendor advice is labelled where we repeat WatchGuard's own guidance. Inventory, prioritisation and network restrictions are our advice.
Inventory every Dimension VM
Our advice is to find every WatchGuard Dimension instance in your own estate and at every client site you manage, and record the running version. Anything from 2.0 up to but not including 2.3.2 is affected.
Upgrade to Dimension 2.3.2
This is the vendor fix. WatchGuard lists Dimension 2.3.2 as the solution for CVE-2026-86130 and the 14 related advisories. Below 2.3, WatchGuard's route is a new 2.3 or higher instance plus a database migration, with 2.1.2 Update 4 needed first if you are on 2.1.2 Update 3 or lower. Confirm System Settings > Dimension System Information shows 2.3.2(752514) afterwards.
Keep Dimension off the internet
Our advice. Keep the Dimension web UI and log collection ports off the internet. Allow them only from managed Fireboxes and your admin VLAN. This reduces exposure while you patch and afterwards. It is not a vendor workaround.
Cut back Dimension administrators
Our advice. Review Dimension administrator accounts and remove low-privileged administrators you do not need. CVE-2026-84322, CVE-2026-86094 and CVE-2026-93915 start from a low-privileged account, and CVE-2026-93916 lets an existing Super Administrator session outlive a downgrade or deletion.
All 15 Dimension CVEs fixed in 2.3.2 (WatchGuard)
Scores are CVSS 4.0, as published by WatchGuard on 19 November 2026. Every entry affects Dimension 2.0 up to but not including 2.3.2. WatchGuard says it is not aware of exploitation in the wild for any of them.
| CVE | Severity (CVSS 4.0) | What it allows | Who can trigger it |
|---|---|---|---|
| CVE-2026-86130 | Critical 9.3 | Missing authentication in the log collection service. Arbitrary SQL, then code execution as the Dimension WebUI process user | Remote, unauthenticated attacker |
| CVE-2026-84322 | Critical 9.3 | Session tokens of logged-in administrators, including Super Administrators, exposed in a management API response | Low-privileged Dimension Administrator |
| CVE-2026-86094 | Critical 9.3 | Session tokens exposed in the web UI diagnostic log. WatchGuard says this is a secondary unmitigated attack path for CVE-2026-78174 | Low-privileged Dimension Administrator |
| CVE-2026-93911 | High 8.7 | SQL injection in the log collector leading to code execution on the appliance | Authenticated managed device, or anyone holding a valid device logging key |
| CVE-2026-93912 | High 8.7 | Code injection in log notification processing leading to code execution on the appliance | Authenticated managed device, or anyone holding a valid device logging key |
| CVE-2026-93914 | High 8.6 | Crafted database snapshot restore runs operating system commands as root | Authenticated Dimension Administrator |
| CVE-2026-103580 | High 8.6 | OS command injection in package update runs commands as root | Authenticated Dimension Administrator |
| CVE-2026-103579 | High 8.6 | CRLF injection in outgoing email server settings runs commands as the local mail-handling account | Authenticated Dimension Administrator |
| CVE-2026-81430 | High 8.6 | Crafted upgrade archive creates or overwrites arbitrary files on the appliance | Authenticated administrator |
| CVE-2026-86126 | High 8.6 | Cross-site request forgery that creates a persistent local Super Administrator account | Remote attacker who tricks a logged-in Super Administrator into visiting a malicious page |
| CVE-2026-93916 | High 8.6 | Super Administrator privileges kept in an existing session after the account is downgraded or deleted | Holder of a valid Super Administrator web UI session |
| CVE-2026-93917 | High 8.6 | Device registration flaw lets one enrolled device take over another device identity and its queued configuration | Attacker who controls one enrolled managed device's credentials |
| CVE-2026-93915 | High 7.7 | Missing authorisation in a legacy system settings handler allows commands with elevated privileges on the OS | Low-privileged authenticated user |
| CVE-2026-126037 | Medium 5.3 | Broken access control exposes detailed device summary data | Low-privileged authenticated user |
| CVE-2026-81434 | Medium 4.8 | Reflected cross-site scripting in the Device Configuration History page | Authenticated user with view permission who sends a victim a crafted link |
Only three are Critical: CVE-2026-86130, CVE-2026-84322 and CVE-2026-86094. Only CVE-2026-93914 and CVE-2026-103580 run commands as root. CVE-2026-93911 and CVE-2026-93912 are not unauthenticated: they need an authenticated managed device or a valid device logging key, so an attacker with a compromised Firebox or a leaked logging key could use them.
Free Detection Pack
Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Check exposure offline and hunt for signs of misuse. Everything is read-only. It covers all 15 CVEs fixed in Dimension 2.3.2.
check-dimension-86130.sh
A read-only, offline bash checker. Give it the Version shown in System Settings > Dimension System Information, a build number, or a text file with those lines copied in. It reports FIXED, AFFECTED or REVIEW OR UNKNOWN against WatchGuard's range (2.0 up to but not including 2.3.2) and prints WatchGuard's new-instance upgrade note for releases below 2.3. It never uses the network, never writes a file and never runs another program.
bash check-dimension-86130.sh --version-string "2.3.2(752514)"
bash check-dimension-86130.sh --file dimension-system-info.txtCheck-Dimension86130.ps1
The same read-only checker in PowerShell 7, with the same inputs, output and exit codes.
pwsh -File Check-Dimension86130.ps1 -File dimension-system-info.txt8 KQL hunts and 4 Sigma rules
8 KQL hunts over firewall (CommonSecurityLog), endpoint network (DeviceNetworkEvents) and Syslog data, and 4 Sigma rules. They look for the Dimension web UI, SSH or log collection port reached from outside your Firebox and admin ranges, new sources of log traffic, unexpected outbound connections from the Dimension VM, user and device changes, and Fireboxes that stop sending logs. All are labelled OUR PATTERN, not vendor signatures. The KQL has not been run against a live tenant. Fill in your Dimension, Firebox and admin ranges first.
Port note: WatchGuard documents TCP 4115 as the port Fireboxes use to send log messages to Dimension. WatchGuard's advisory does not name the port of the affected log collection service. The pack treats 4115 as that service, and that is our assumption.
Sigma rules (our pattern):
Reactive: How to Hunt (Our Advice)
The hunts below are CybaVerse advice, not vendor advice. WatchGuard's advisories describe the flaws and the fix. They do not publish a hunt list or indicators of compromise, and this page invents none.
Look for unknown Admin or Super Admin accounts
Review Dimension user management for administrator or Super Administrator accounts nobody can account for, and for privilege changes you did not make. CVE-2026-86126 can create a persistent local Super Administrator.
Look for unexpected device registrations
Compare the devices registered in Dimension with your real Firebox inventory. Look for new, duplicated or changed device registrations, and configuration pushed to a Firebox that nobody scheduled.
Check the log collector for odd SQL errors and requests
Review Dimension log collection service logs for unusual SQL errors, malformed or unexpected requests, and connections from sources that are not your managed Fireboxes.
Watch the VM for new processes and outbound traffic
Look for new or unexpected processes on the Dimension VM, and outbound connections from it to anything other than the destinations it normally talks to.
Isolate, rotate, rebuild
Our advice: isolate the Dimension VM and keep its logs. Rotate Dimension administrator credentials and Firebox management credentials. Rebuild from a clean Dimension 2.3.2 image rather than patching a compromised VM, and engage incident response.
How CybaVerse helps
CybaOps brings proactive checks, reactive hunting and the fix into one product through our FAFO model: Find, Analyse, Fix, Operate.
Find every Dimension VM
We help you find every WatchGuard Dimension instance across your own estate and the client estates you manage, including the forgotten ones still on 2.x builds.
Hunt the signs that matter
UK-based analysts run the hunts above against Dimension and Firebox telemetry, and tune them to your environment so you are not left with an unused query pack.
Drive the upgrade to a verified fix
CybaOps drives remediation, including the Dimension 2.3.2 upgrade, access lock-down and any rebuild, through to a verified fix rather than leaving a ticket open.
Keep watching after the patch
Analysts monitor alerts 24/7 and act on pre-approved response actions, so the team that helped you patch keeps watching for later misuse of your firewall management.
WatchGuard Dimension CVE-2026-86130 FAQ
Short answers based on WatchGuard's PSIRT advisories, the NVD record, and a CISA KEV check at 20:59 GMT on 19 November 2026. Last updated 19 November 2026, 20:59 GMT.
Am I affected?
Yes if you run WatchGuard Dimension 2.0 or later, up to but not including 2.3.2. WatchGuard lists Dimension 2.3.2 and later as not affected. Dimension is the on-premises log and reporting virtual machine used with Firebox appliances, so check every client site you manage as well as your own.
What is the severity?
WatchGuard rates CVE-2026-86130 Critical at CVSS 4.0 9.3, with the vector AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. That means network reachable, low complexity, and no privileges or user interaction needed. The NVD record shows WatchGuard's score and NVD had not added its own score when we checked.
What does an attacker get?
WatchGuard says missing authentication in the Dimension log collection service lets a remote, unauthenticated attacker run arbitrary SQL statements and then run arbitrary code as the Dimension WebUI process user, by sending specially crafted network requests. Dimension holds Firebox logs and reports, so our advice is to treat a compromised Dimension VM as a foothold into your firewall management.
Has this been exploited?
No exploitation reported as of 19 November 2026. WatchGuard says it is not aware of any exploitation of this vulnerability in the wild. CVE-2026-86130 was not in CISA's Known Exploited Vulnerabilities catalogue when we checked at 20:59 GMT on 19 November 2026 (catalogue version 2026.11.18). Absence from that catalogue does not prove there has been no exploitation.
What is the fix?
Upgrade Dimension to 2.3.2. WatchGuard lists 2.3.2 as the solution for CVE-2026-86130 and for the 14 other Dimension advisories it published on 19 November 2026. The advisories do not list a workaround. From 2.3 or higher, apply the 2.3.2 upgrade file. Below 2.3, WatchGuard's release notes say to deploy a new 2.3 or higher instance and migrate the database, and from 2.1.2 Update 3 or lower to install 2.1.2 Update 4 first. Confirm the running version after you update.
What else does Dimension 2.3.2 fix?
WatchGuard published 15 Dimension advisories on 19 November 2026, all fixed in 2.3.2. Three are Critical 9.3: CVE-2026-86130, plus CVE-2026-84322 and CVE-2026-86094, which let a low-privileged Dimension Administrator steal a Super Administrator's session token. Ten are High, from 7.7 to 8.7, including code execution as root through snapshot restore (CVE-2026-93914) and package update (CVE-2026-103580), a CSRF that creates a Super Administrator (CVE-2026-86126) and device registration takeover (CVE-2026-93917). Two are Medium.
I patched CVE-2026-78174 in August. Am I covered?
No. CVE-2026-78174 was fixed in Dimension 2.3.1. WatchGuard says CVE-2026-86094 is a secondary unmitigated attack path for CVE-2026-78174, and it affects Dimension 2.0 up to but not including 2.3.2. Move to 2.3.2.
Can I restrict access instead of patching?
Not as a fix. Our advice is to keep the Dimension web UI and log collection ports off the internet, reachable only from managed Fireboxes and your admin VLAN, until and after you upgrade. That reduces exposure. It is not a vendor workaround and does not replace Dimension 2.3.2.
What should I do if I suspect compromise?
This is our advice, not vendor advice. Isolate the Dimension VM and keep its logs. Rotate Dimension administrator credentials and Firebox management credentials. Rebuild from a clean Dimension 2.3.2 image rather than patching a compromised VM, and engage incident response.
Need help finding Dimension across the estates you manage?
CybaOps monitors your servers, endpoints and cloud workloads, whether that's your own business or your clients'. UK-based analysts monitor alerts 24/7, run these threat hunts and act on pre-approved response actions, and CybaOps drives remediation through to a verified fix, so proactive checks and reactive response happen in one place.
Sources
- WatchGuard PSIRT, CVE-2026-86130, Dimension Improper Authentication in Log Collection Service Allows Unauthenticated Remote Code Execution (published 19 November 2026)
- WatchGuard Security Advisories, listing all 15 Dimension CVEs published on 19 November 2026 (each CVE in the table above links to its own advisory)
- WatchGuard Dimension 2.3.2 release notes (build 752514, release date 19 November 2026), for the upgrade path
- WatchGuard PSIRT, CVE-2026-78174 (published 27 August 2026, fixed in Dimension 2.3.1)
- NVD record for CVE-2026-86130 (published 19:17 GMT on 19 November 2026)
- CISA Known Exploited Vulnerabilities catalogue (checked 20:59 GMT on 19 November 2026; catalogue version 2026.11.18)