# CVE-2026-131237: Search Processing Language Injection through Weak Encrypted Communication Drilldowns in Splunk Enterprise Security

> A user with run_collect capability can plant SPL commands in the Weak Encrypted Communication report that run with another user's permissions; Splunk Enterprise Security admins should care.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 20 Nov 2026
- **Also known as:** GHSA-wfjr-j7xc-59h9

## What is CVE-2026-131237?

CVE-2026-131237 is a medium-severity code injection vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in data used by the Weak Encrypted Communication report. If another user who can access the report selects an affected drilldown, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the drilldown. The user who stores the values could then access sensitive data and modify some data available to the user who selects the drilldown.
The vulnerability is possible because the Weak Encrypted Communication report does not validate source, destination, and Secure Sockets Layer version values before inserting them into drilldown searches.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Weak Encrypted Communication (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/weak-encrypted-communication) in the Splunk documentation.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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

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


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

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

## Is CVE-2026-131237 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131237 is a medium-severity code injection vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-131237 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-131237/ (Markdown: https://insights.sbomify.com/CVE-2026-131237/index.md)
```

## Sources

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

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