CVE-2026-131231
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 managed-…
Impact
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 managed-lookup audit data. If another user who can access the Managed Lookups Audit dashboard selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify some data available to the user who selects the row. The vulnerability is possible because the Managed Lookups Audit dashboard does not safely escape audit data before inserting it 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 Audit dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/audit-dashboards) in the Splunk documentation.
An attacker can exploit this over the network, with a regular user account, but a user has to do something, such as open a file or a link. Specific conditions have to be met, which makes an attack harder. If it succeeds: high risk of data being read, low risk of data or systems being changed.
Affected products · Splunk
| Product | Affected versions |
|---|---|
| Splunk Enterprise Security | before 8.7.0 |