Splunk Enterprise Security stored SPL injection in finding exclusion rules
- Exploited
- No known exploitation
- Fix
- Fixed in 8.7.0
- Who is exposed
- Not reported
Summary
Splunk Enterprise Security has a flaw in its Finding Exclusion Rules page that lets a remote attacker with a low-privilege login run attacker-supplied Search Processing Language (SPL) commands. The attacker stores malicious data in exclusion rule metadata, and the commands run when another authenticated user opens the page, letting the attacker access data and perform actions available to that user.
Written by a model
Original 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 (help.splunk.com/
What to do
Upgrade 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-131213 (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-131213 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise Security: fixed in 8.7.0
Fixed versions: 8.7.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131213 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131213 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-131213
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-131213"}.Affected versions
- Splunk Splunk Enterprise Securityfixed in 8.7.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.7/10CVSS 6.7
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
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-131213 |
| Record | NVD · CVE-2026-131213 |
Questions about CVE-2026-131213
Is CVE-2026-131213 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
Which versions are affected by CVE-2026-131213?
Splunk Enterprise Security: before 8.7.0.
Source: cve.now feed data
How do I fix CVE-2026-131213?
Upgrade to a fixed version: 8.7.0.
Source: cve.now feed data
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.