In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_admin" Splunk Enterprise Security role
Source GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 8.7.0 as a priority.
Data as of 19 Nov 2026, 22:48 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 9.1 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation 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
If you cannot patch yet, restrict the assignment of the "ess_admin" role to trusted users only and monitor for unusual activity related to lookup file uploads and Configuration Checker usage.
Description
In Splunk Enterprise Security versions below 8.7.0, users with the "ess_admin" role can execute arbitrary code on the search head by exploiting unrestricted lookup file uploads combined with Configuration Checker functionality. This occurs because the product does not restrict lookup file types nor confines Configuration Checker module paths to intended directories.