In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role
Source GCVE Database
Not known to be exploited · CVSS 7.6 High · fixed in 10.4.5 : patch Splunk Enterprise soon.
Data as of 19 Nov 2026, 22:54 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 7.6 |
|---|
- Patch
- Available – fixed in 10.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:LExploitation 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, 10.0.12 or 9.4.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
Users should apply updates to versions 10.4.5, 10.2.9, 10.0.12, or 9.4.17 once released by the vendor. Until then, restrict the assignment of the "power" role to trusted users only and educate users to avoid opening untrusted dashboards. Monitor vendor advisories for official fixes and guidance.
Description
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where a user with the "power" role can store malicious Search Processing Language (SPL) in a shared dashboard. This malicious SPL executes with the permissions of the user who opens the dashboard, potentially allowing unauthorized data access, modification, or disruption of service. The vulnerability arises from improper handling of quoted search argument boundaries in dashboard searches. Exploitation requires phishing to trick a user into opening a crafted dashboard, and the attacker must have the "power" role. No public exploits or patches are currently documented.