In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who holds the "power" Splunk role
Source GCVE Database
Not known to be exploited · CVSS 7.6 High · fixed in 10.4.4 : 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.4, 10.2.8, 10.0.11 +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.4, 10.2.8, 10.0.11 or 9.4.16.
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
The vulnerability affects versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16. Users should upgrade to at least these fixed versions to remediate the issue. Additionally, restrict the "power" role to trusted users and educate users to avoid opening suspicious alert links to reduce phishing risk.
Description
Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 contain a vulnerability where a user with the "power" role can create and share a metric alert that executes malicious Search Processing Language (SPL) code when another authenticated user opens the alert link. This occurs because Analytics Workspace does not fully sanitize metric alert names before embedding them in SPL. Exploitation requires phishing to trick a user into opening the malicious alert link. The vulnerability can lead to data exposure, data modification, or service disruption in the affected session.