In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could
Source GCVE Database
Not known to be exploited · CVSS 6.4 Medium · fixed in 10.4.2 : update Splunk Enterprise when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.2, 10.2.6, 10.0.9 +1
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 Aug 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 18 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.2, 10.2.6, 10.0.9 or 9.4.14.
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.2, 10.2.6, 10.0.9, and 9.4.14. Users should upgrade to at least these fixed versions to remediate the issue. Until patched, restrict the assignment of the "power" role and educate users to be cautious of phishing attempts that could trigger malicious workflow actions.
Description
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a vulnerability exists where a user with the "power" role can store a Dashboard Studio workflow action containing attacker-controlled Search Processing Language (SPL). When another authenticated user triggers this action and continues, the injected SPL executes with that user's permissions, potentially allowing unauthorized data access or modification. The flaw arises from insufficient validation of workflow-action URLs in Dashboard Studio. Exploitation requires phishing to trick users into initiating the malicious request. Users with the "power" role cannot exploit this vulnerability at will.