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 that populates the Endpoint Changes report. Another user who holds the "pci_analyst" role could later click a corresponding table row. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access or modify data available to that user.
The vulnerability is possible because the Endpoint Changes report does not treat dynamic report values as literal search values when it builds table-row drilldown searches.
For more information see 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) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation.
Published: 2026-11-19
Score: 3.7 Low
EPSS: n/a
KEV: No
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

Vendor Solution

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


Vendor Workaround

Turn off or remove the Splunk App for PCI Compliance. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 19 Nov 2026 20:15:00 +0000

Type Values Removed Values Added
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 that populates the Endpoint Changes report. Another user who holds the "pci_analyst" role could later click a corresponding table row. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access or modify data available to that user. The vulnerability is possible because the Endpoint Changes report does not treat dynamic report values as literal search values when it builds table-row drilldown searches. For more information see 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) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation.
Title SPL Injection through the Endpoint Changes Report in Splunk Enterprise Security
Weaknesses CWE-116
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

Updated: 2026-11-19T20:38:40.716Z

Reserved: 2026-11-17T20:26:14.304Z

Link: CVE-2026-131224

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-19T20:17:36.623

Modified: 2026-11-19T20:17:36.623

Link: CVE-2026-131224

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses