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.1 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.1 |
|---|
- 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: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 Security to 8.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise Security | Affected
| Fixed in
|
AI-suggested
Splunk Enterprise Security version 8.7.0 or later includes fixes that address this vulnerability. Users should upgrade to version 8.7.0 or later to remediate this issue. Until upgraded, restrict 'ess_analyst' role permissions or monitor saved searches closely to mitigate risk.
Description
In Splunk Enterprise Security versions below 8.7.0, users with the 'ess_analyst' role can create saved searches that are attacker-controlled. These saved searches may be executed later with elevated permissions during threat intelligence lookup generation, allowing the user to run arbitrary Search Processing Language (SPL) commands with those elevated privileges. This occurs because the system does not properly restrict which saved searches are used for threat intelligence lookup generation.