Skip to main content
Menu
CVEs

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.

CVE-2026-131209Published November 19, 2026, updated

8.3HighCNA
Exploited
No known exploitation
Fix
Fixed in 8.7.0
Who is exposed
Specific setups only

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

Original 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 (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 (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 (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.

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.

“In Splunk Enterprise Security versions below 8.7.0”

advisory.splunk.com

What to do

  1. Check whether your setup matches what the bug needs.

    Splunk Enterprise Security versions below 8.7.0 The UEBA Content App is installed and processes Entity Risk Score calculations
  2. Upgrade to a fixed version: 8.7.0.

  3. Workaround: Turn off or remove the UEBA Content App.

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-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"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.3/10CVSS 8.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkadvisory.splunk.com · advisories/SVD-2026-1106
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-131209
RecordNVD · CVE-2026-131209

Questions about CVE-2026-131209

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: cve.now feed data

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: advisory.splunk.com, cve.org

Which versions are affected by CVE-2026-131209?

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 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: advisory.splunk.com, cve.org

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: advisory.splunk.com, cve.org

No corrections so far. Something wrong on this page? Report an error.