In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could
Source GCVE Database
Not known to be exploited · CVSS 6.4 Medium : upgrade to 8.7.0 when convenient.
Data as of 19 Nov 2026, 22:40 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 6.4 |
|---|
- Patch
- Available – fixed in 8.7.0
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 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 newer to remediate this vulnerability. Until then, restrict roles with the run_collect capability to trusted users only and monitor usage of the Secure Sockets Layer Search dashboard. No vendor advisory content was provided to indicate alternative mitigations or temporary fixes.
Description
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can store attacker-controlled certificate values. When another user with access to the Secure Sockets Layer Search dashboard selects an affected row, the system may execute attacker-controlled Search Processing Language (SPL) commands with the permissions of the selecting user. This occurs because the dashboard encodes certificate values for drilldown links but does not properly escape them as SPL search literals. This flaw can lead to unauthorized data access and modification by the user who initially stored the malicious values.