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 5.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 | 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
Users should upgrade to Splunk Enterprise Security version 8.7.0 or later where this issue is resolved. Until then, restrict the run_collect capability to trusted roles only and limit access to the Weak Encrypted Communication report to minimize exposure. Monitor Splunk's official advisories for patch availability and apply updates promptly once released.
Description
Splunk Enterprise Security versions below 8.7.0 contain a vulnerability where a user with the run_collect capability can inject attacker-controlled values into the Weak Encrypted Communication report. This can lead to another user executing attacker-controlled SPL commands with their permissions when interacting with the report's drilldown feature. The flaw arises from insufficient validation of certain report data before use in drilldown searches.