CVE-2026-131219: SPL Injection through the Network Traffic Activity Report in Splunk Enterprise Security
In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the runcollect capability could store attacker-controlled values in network traffic data. Another user who holds the "pciuser" 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk Enterprise Securityto a version that resolves this vulnerability.Fixed in 8.7.0 - Upgrade
Upgrade
Splunk App for PCI Complianceto a version that resolves this vulnerability.Fixed in 8.7.0