Skip to content
Applications

CVE-2026-66147

9.4
Critical
EPSS 2%Aug 12, 2026

Unauthenticated command injection in GMS Dispatcher Service allowing remote code execution.

common questions

Is CVE-2026-66147 being exploited?

Not confirmed. CVE-2026-66147 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.0% probability of exploitation in the next 30 days.

How severe is CVE-2026-66147?

CVE-2026-66147 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-66147?

Not known from our data. No patch reference has been recorded for CVE-2026-66147, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-66147 affect?

CVE-2026-66147 affects GMS Dispatcher Service, GMS version 9.5.1 and earlier, Servers exposing Dispatcher API. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-66147?

Isolate/disable Dispatcher service from untrusted networks, block access, and apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
GMS Dispatcher ServiceGMS version 9.5.1 and earlierServers exposing Dispatcher API
impact

Unauthenticated remote code execution via crafted requests; attacker can execute arbitrary commands, fully compromise host and pivot laterally.

action required

Immediate action required

affected versions
SonicWall GMS
  • affected9.5.1 and earlier versions

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free