# CVE-2026-131209: SPL Injection through the REST API in Splunk Enterprise Security

> Users with a specific capability can inject SPL via Entity Risk Score in Splunk Enterprise Security, exposing stored credentials.

- **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-5gmx-jvhh-vq5j

## What is CVE-2026-131209?

CVE-2026-131209 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_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.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

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


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

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

## Is CVE-2026-131209 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131209 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-131209 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-131209/ (Markdown: https://insights.sbomify.com/CVE-2026-131209/index.md)
```

## Sources

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

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