In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role
Source GCVE Database
Not known to be exploited · CVSS 8.3 High : upgrade to 8.7.0 soon.
Data as of 19 Nov 2026, 22:48 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 8.3 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Security to 8.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise Security | Affected
| Fixed in
|
AI-suggested
A fix is available in Splunk Enterprise Security version 8.7.0 and later. Users should upgrade to version 8.7.0 or above to remediate this vulnerability. Until then, review and restrict the permissions of the "ess_analyst" role to prevent unauthorized modification of search macros associated with risk exclusions.
Description
In Splunk Enterprise Security versions below 8.7.0, users with the "ess_analyst" role can modify a search macro related to risk exclusions. This allows scheduled risk data model acceleration searches to execute attacker-controlled SPL commands with elevated permissions. Exploitation could lead to exposure of stored credentials and unauthorized modification of indexes or lookup data.