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 4.6 Medium : upgrade to 8.7.0 when convenient.
Data as of 19 Nov 2026, 22:50 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 4.6 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/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
A fix is available starting with Splunk Enterprise Security version 8.7.0. Users should upgrade to version 8.7.0 or later to remediate this vulnerability. No other mitigation or workaround is specified in the available data.
Description
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into intrusion detection data. A user with the pci_user role can then trigger a report that executes attacker-controlled Search Processing Language (SPL) commands with their permissions. This occurs because the Intrusion Detection and Prevention System Alert Activity report does not properly treat intrusion detection values as literal search inputs when constructing drilldown searches.