CVE-2026-131219 SPL Injection through the Network Traffic Activity Report in Splunk Enterprise Security

Low 3.7 Published Updated

A user with run_collect capability can plant SPL in traffic data that runs as another user clicking the report in Splunk Enterprise Security.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Harmful if only installed
No
Needs a specific call
No
Fix
None listed

What is CVE-2026-131219?

CVE-2026-131219 is a low-severity code injection vulnerability in Splunk App for PCI Compliance, published on 19 Nov 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official 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.

Weakness: CWE-943

Which versions are affected by CVE-2026-131219?

An affected version is exposed as installed. No special setting or call is needed.

How do I fix CVE-2026-131219?

No fix has been published for CVE-2026-131219 yet. Limit exposure of the affected software until one is available.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2026-131219 being exploited?

There is no known exploitation of CVE-2026-131219 in the wild and no public exploit code.

Sources

Also known as GHSA-5f4r-pjpq-654w.

Is CVE-2026-131219 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free