In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the edit_timeline capability could store attacker-controlled Search Processing Language (SPL) in a legacy investigation timeline entry. Another user that holds a role with the manage_all_investigations capability could later open the investigation and select Run Search from the timeline. Splunk Enterprise Security could then run the SPL stored by the first user using the permissions of the user who selected Run Search. The SPL stored by the first user could access data or perform actions available to the user who selected Run Search.
The vulnerability is possible because Splunk Enterprise Security does not treat stored investigation search content as a literal search before building the Search page link.
For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.3/installation/capability-reference-for-splunk-enterprise-security) and Add details to an investigation in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-7/user-guide/7.3/investigations/add-details-to-an-investigation-in-splunk-enterprise-security) in the Splunk documentation.

Project Subscriptions

No data.

Advisories

No advisories yet.

Fixes

Solution

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


Workaround

Turn off or remove the Splunk Enterprise Security app. 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.

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 edit_timeline capability could store attacker-controlled Search Processing Language (SPL) in a legacy investigation timeline entry. Another user that holds a role with the manage_all_investigations capability could later open the investigation and select Run Search from the timeline. Splunk Enterprise Security could then run the SPL stored by the first user using the permissions of the user who selected Run Search. The SPL stored by the first user could access data or perform actions available to the user who selected Run Search. The vulnerability is possible because Splunk Enterprise Security does not treat stored investigation search content as a literal search before building the Search page link. For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.3/installation/capability-reference-for-splunk-enterprise-security) and Add details to an investigation in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-7/user-guide/7.3/investigations/add-details-to-an-investigation-in-splunk-enterprise-security) in the Splunk documentation.
Title SPL Injection through Legacy Investigation Timeline Search Actions in Splunk Enterprise Security
Weaknesses CWE-943
References
Metrics cvssV3_1

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


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

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

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

Link: CVE-2026-131214

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

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

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

Link: CVE-2026-131214

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses