Skip to main content
Menu
CVEs

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.

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

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

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

Original 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 (help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Reports (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.

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

“In Splunk App for Payment Card Industry Compliance versions below 8.7.0”

advisory.splunk.com

What to do

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

    Splunk App for Payment Card Industry Compliance versions below 8.7.0 Another authenticated user must select the attacker-supplied value in the Primary Function Summary panel
  2. Upgrade to a fixed version: 8.7.0.

  3. Workaround: Turn off or remove the Splunk App for Payment Card Industry Compliance.

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

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.3/10CVSS 7.3
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

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-131211
RecordNVD · CVE-2026-131211

Questions about CVE-2026-131211

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

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

Which versions are affected by CVE-2026-131211?

Splunk Enterprise Security: before 8.7.0.

Source: cve.now feed data

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

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

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