# CVE-2026-131215: SPL Injection through Finding Exclusion Rules in Splunk Enterprise Security

> Users with a specific role can store malicious SPL in UEBA exclusion rules, running commands with elevated permissions to read credentials and modify lookups.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 21 Nov 2026
- **Also known as:** GHSA-9wmq-3v2q-x4jr

## What is CVE-2026-131215?

CVE-2026-131215 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, with no action from the victim.

### Official description

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_finding_exclusion_edit capability could store attacker-controlled values in a User and Entity Behavior Analytics (UEBA) finding exclusion rule. Splunk Enterprise Security could later run attacker-controlled Search Processing Language (SPL) commands from the rule with elevated permissions. With this access, the user could cause Splunk Enterprise Security to read stored credentials and modify lookups and knowledge objects.
The vulnerability is possible because the UEBA finding exclusion workflow does not escape user-controlled rule values before using them in generated SPL.
For more information see Create a finding exclusion rule using UEBA configuration page (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/user-and-entity-behavior-analytics/finding-exclusions-in-splunk-enterprise-security/create-a-finding-exclusion-rule-using-ueba-configuration-page) 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-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-131215?

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


## How do I fix CVE-2026-131215?

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

## Is CVE-2026-131215 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-131215 and fix it if it is affected.

What it is: CVE-2026-131215 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, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-131215 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Splunk Enterprise Security. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-131215/ (Markdown: https://insights.sbomify.com/CVE-2026-131215/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-131215
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-131215
- OSV: https://osv.dev/vulnerability/CVE-2026-131215

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-131215/
Summaries are generated and may contain mistakes; the official description above is the record.
