CVE-2026-131213 SPL Injection through Finding Exclusion Rules in Splunk Enterprise Security
A low-privileged Splunk ES user can plant SPL in exclusion rule metadata that runs with the permissions of users viewing the exclusion rules page.
- 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-131213?
CVE-2026-131213 is a medium-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 Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could store attacker-controlled data in finding exclusion rule metadata. Another authenticated user could later open the Finding Exclusion Rules page. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who opened the page. The first user could access data and perform actions available to the later user. The vulnerability is possible because Splunk Enterprise Security does not escape backslashes in finding exclusion rule metadata before adding the values to a page search. For more information see Finding exclusions in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/user-and-entity-behavior-analytics/finding-exclusions-in-splunk-enterprise-security) and 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) in the Splunk documentation.
Weakness: CWE-116
Which versions are affected by CVE-2026-131213?
An affected version is exposed as installed. No special setting or call is needed.
How do I fix CVE-2026-131213?
No fix has been published for CVE-2026-131213 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-131213 being exploited?
There is no known exploitation of CVE-2026-131213 in the wild and no public exploit code.
Sources
Also known as GHSA-5pr3-2q4c-xfr9.