CVE-2026-131211 SPL Injection through the Primary Functions Report in Splunk Enterprise Security

High 7.3 Published Updated

A low-privileged Splunk user can plant SPL in report values that runs with another user's permissions when they click it.

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-131211?

CVE-2026-131211 is a high-severity code injection vulnerability in Splunk Enterprise Security, 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 App for Payment Card Industry Compliance versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could add attacker-controlled values to lookup data used by the Primary Functions report. If another authenticated user later selects the value in the Primary Function Summary panel, the Splunk App for Payment Card Industry Compliance could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the value. With this access, the first user could expose or modify data available to the user who selected the value. The vulnerability is possible because the Primary Functions report does not safely escape report values before including them in drilldown searches. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Reports (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/user-manual/8.7/using-the-splunk-app-for-pci-compliance/reports) in the Splunk documentation.

Weakness: CWE-943

Which versions are affected by CVE-2026-131211?

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

How do I fix CVE-2026-131211?

No fix has been published for CVE-2026-131211 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-131211 being exploited?

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

Sources

Also known as GHSA-hxgr-xx8p-2939.

Is CVE-2026-131211 in your software?

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

Check your SBOMs for free