In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 8.7.0 when convenient.
Data as of 19 Nov 2026, 22:54 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.4 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/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
Since the vulnerability requires interaction between two users and specific roles, organizations should review role assignments and restrict the ess_user and mc_assets_read capabilities to trusted users. Monitor Splunk Enterprise Security updates and apply official patches once available. Until then, limit exposure by controlling user permissions related to asset data management and Asset Center dashboard access.
Description
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the "ess_user" role can store attacker-controlled asset data in an asset source lookup. This data can later be selected by another user with the mc_assets_read capability in the Asset Center dashboard, leading to execution of attacker-controlled SPL commands with the permissions of that user. The issue arises because Asset Center does not properly escape asset values before using them in drilldown searches. Exploitation requires two users: one to store the malicious data and another to select it, limiting direct exploitation by the initial user.