CVE-2026-131214: SPL Injection through Legacy Investigation Timeline Search Actions in Splunk Enterprise Security
This Splunk advisory covers CVE-2026-131214 in Splunk Enterprise Security.
- CVE-2026-131214
Key facts
- Vendor rating
- Medium, CVSS 4.8
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N· base score 4.8, scored by ciscoAttack vector: network. Attack complexity: high. Privileges required: low. User interaction: required. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.- Weakness
- CWE-943 The application generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Splunk Enterprise Security before 8.7.0
- Fixed in
- 8.7.0
- Source published
- Source revised
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
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 ( ) and Add details to an investigation in Splunk Enterprise Security ( ) in the Splunk documentation.
Text from the source record.
- Splunk Enterprise Security before 8.7.0
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-131214
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- 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.
End-of-life dates for Splunk Enterprise
More Splunk advisories
CVE-2026-131239Nov 19, 2026SPL Injection through the System Update Status Report in Splunk Enterprise SecurityCVE-2026-131238Nov 19, 2026Search Processing Language (SPL) Injection through the Secure Sockets Layer SearchCVE-2026-131237Nov 19, 2026Search Processing Language Injection through Weak Encrypted Communication DrilldownsCVE-2026-131236Nov 19, 2026SPL Injection through Splunk Web Workflow Actions in Splunk Enterprise SecurityCVE-2026-131235Nov 19, 2026SPL Injection through the Credit Card Data Found Dashboard in Splunk Enterprise SecurityCVE-2026-131234Nov 19, 2026SPL Injection through the Entity Analysis Dashboard in Splunk Enterprise Security
Get an email when Splunk Enterprise publishes the next one.
See Splunk Enterprise's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.