In Splunk Enterprise versions below 10.4.5, 10.2.9, and 10.0.12, a low-privileged user who holds the "power" Splunk
Source GCVE Database
Not known to be exploited · CVSS 6.4 Medium · fixed in 10.4.5 : update Splunk Enterprise when convenient.
Data as of 19 Nov 2026, 22:55 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 6.4 |
|---|
- Patch
- Available – fixed in 10.4.5, 10.2.9, 10.0.12
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.5, 10.2.9 or 10.0.12.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
A fix is available in Splunk Enterprise versions 10.4.5, 10.2.9, and 10.0.12, which correct the permissions granted to the "power" role for shared dashboard views. Users should upgrade to these or later versions to remediate the vulnerability. Until patched, restrict the assignment of the "power" role to trusted users only and avoid sharing dashboards with write access to this role.
Description
A vulnerability in Splunk Enterprise versions below 10.4.5, 10.2.9, and 10.0.12 allows a low-privileged user with the "power" role to overwrite shared dashboard views with arbitrary SPL commands. These commands execute with the permissions of any authenticated user who views the dashboard, potentially exposing or modifying data accessible to that user. The issue arises because the Splunk App for Splunk Observability Cloud incorrectly grants write access to shared dashboards to the "power" role instead of restricting it to the "admin" role.