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 3.7 Low : 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 | 3.7 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/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 App for PCI Compliance to 8.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk App for PCI Compliance | Affected
| Fixed in
|
AI-suggested
Upgrade to Splunk Enterprise Security version 8.7.0 or later where this issue is fixed. Until upgraded, restrict roles with run_collect capability and pci_user role to trusted users only to reduce risk.
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 network traffic data. Another user with the pci_user role could then trigger execution of attacker-controlled SPL commands by interacting with the Network Traffic Activity report. This occurs because the report does not properly treat network traffic values as literals when constructing drilldown searches, allowing command execution with the permissions of the clicking user.