CVE-2026-131205

SPL Injection through Asset Center Drilldowns in Splunk Enterprise Security

Severity
Medium 5.4
CVSS 3.1
Remote, needs privileges or user interaction what this means
Exploited
Not listed
EPSS
—
Discovered by
Not disclosed
Published
Nov 19, 2026
Assigned by cisco

Description

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could store attacker-controlled asset data in an asset source lookup. A user that holds a role with the mc_assets_read capability could later open the Asset Center dashboard and select that value in the Asset Information table. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of that user. With this access, the user who stored the asset data could expose or modify data available to the user who selected the value. The vulnerability is possible because Asset Center does not escape asset values before adding them to drilldown searches. The vulnerability requires Asset Center to process the asset data and another user to select the value. The user who stored the data should not be able to exploit the vulnerability at will. 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), Add asset and identity data to Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/asset-and-identity-management/add-asset-and-identity-data-to-splunk-enterprise-security), and Asset and identity dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/asset-and-identity-dashboards) in the Splunk documentation.

Weakness: CWE-943

Affected products

Vendor Product Category Matched by
Cisco Splunk Enterprise Security SIEM & Log Management cna-assigner
Vendor-reported products (1)
  • Splunk · Splunk Enterprise Security

Vendor remediation

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

Something wrong here?