Splunk Enterprise Security SPL command injection in UEBA finding exclusions
Affects Splunk Enterprise Security below 8.7.0, where users with the ueba_finding_exclusion_edit capability can inject SPL through UEBA finding exclusion rule values. Fixed in 8.7.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.7.0
- Who is exposed
- Specific setups only
Summary
Written by a model
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 (help.splunk.com/
Who should check
Teams running Splunk Enterprise Security below 8.7.0 that use UEBA finding exclusion rules, and anyone granting the ueba_finding_exclusion_edit capability
“In Splunk Enterprise Security versions below 8.7.0”
What to do
Check whether your setup matches what the bug needs.
Splunk Enterprise Security versions below 8.7.0 The attacker holds a role with the ueba_finding_exclusion_edit capability The UEBA finding exclusion workflow generates SPL from user-controlled rule valuesUpgrade to a fixed version: 8.7.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131215 (SPL Injection through Finding Exclusion Rules in Splunk Enterprise Security), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131215 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise Security: fixed in 8.7.0
Fixed versions: 8.7.0.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise Security versions below 8.7.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
- The attacker holds a role with the ueba_finding_exclusion_edit capability (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
- The UEBA finding exclusion workflow generates SPL from user-controlled rule values (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-131215 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131215 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1106
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131215
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131215"}.Affected versions
- Splunk Splunk Enterprise Securityfixed in 8.7.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1106 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131215 |
| Record | NVD · CVE-2026-131215 |
Questions about CVE-2026-131215
Is CVE-2026-131215 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The UEBA finding exclusion workflow does not escape user-controlled rule values before placing them in generated SPL. A user with the right capability can therefore run attacker-controlled SPL commands with elevated permissions, read stored credentials, and modify lookups and knowledge objects.
Source: advisory.splunk.com
Which versions are affected by CVE-2026-131215?
Splunk Enterprise Security: before 8.7.0.
Source: cve.now feed data
Am I affected, and how do I check?
Splunk Enterprise Security versions below 8.7.0 are affected, but only where a role holds the ueba_finding_exclusion_edit capability. To check, look at the installed Splunk Enterprise Security version and at which roles hold that capability.
Source: advisory.splunk.com
How do I fix CVE-2026-131215?
Upgrade Splunk Enterprise Security to version 8.7.0 or later, which is the fixed version listed for this vulnerability.
Source: advisory.splunk.com
Related
- CVE-2026-131236SPL Injection through Splunk Web Workflow Actions in Splunk Enterprise Security
- CVE-2026-131218SPL Injection through the Mission Control REST API in Splunk Enterprise Security
- CVE-2026-131239SPL Injection through the System Update Status Report in Splunk Enterprise Security
- CVE-2026-131222Privilege Escalation through Asset and Identity Management in Splunk Enterprise Security
- CVE-2026-131238Search Processing Language (SPL) Injection through the Secure Sockets Layer Search Dashboard in Splunk Enterprise Security
- CVE-2026-131232SPL Injection through the Vulnerability Scan Details Splunk Web Dashboard in Splunk Enterprise Security
No corrections so far. Something wrong on this page? Report an error.