In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in network traffic data. Another user who holds the "pci_user" role could later click the corresponding row in the Traffic Detail panel of the Network Traffic Activity report. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access data and perform actions available to that user.
The vulnerability is possible because the Network Traffic Activity report does not treat network traffic values as literal search values when it builds the Traffic Detail drilldown search.
For more information see Network Traffic Activity (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/network-traffic-activity) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation.

Project Subscriptions

No data.

Advisories

No advisories yet.

Fixes

Solution

Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher.


Workaround

Turn off or remove the Splunk App for PCI Compliance. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation.

History

Thu, 19 Nov 2026 20:15:00 +0000

Type Values Removed Values Added
Description In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in network traffic data. Another user who holds the "pci_user" role could later click the corresponding row in the Traffic Detail panel of the Network Traffic Activity report. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access data and perform actions available to that user. The vulnerability is possible because the Network Traffic Activity report does not treat network traffic values as literal search values when it builds the Traffic Detail drilldown search. For more information see Network Traffic Activity (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/network-traffic-activity) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation.
Title SPL Injection through the Network Traffic Activity Report in Splunk Enterprise Security
Weaknesses CWE-943
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

Updated: 2026-11-19T20:38:48.697Z

Reserved: 2026-11-17T20:26:14.303Z

Link: CVE-2026-131219

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-19T20:17:36.007

Modified: 2026-11-19T21:17:55.593

Link: CVE-2026-131219

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses