CVE-2026-131215: SPL Injection through Finding Exclusion Rules in Splunk Enterprise Security
This Splunk advisory covers CVE-2026-131215 in Splunk Enterprise Security.
- CVE-2026-131215
Key facts
- Vendor rating
- High, CVSS 8.3
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L· base score 8.3, scored by ciscoAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: low.- Weakness
- CWE-74 The software constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Splunk Enterprise Security before 8.7.0
- Fixed in
- 8.7.0
- Source published
- 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 ueba_finding_exclusion_edit capability could store attacker-controlled values in a User and Entity Behavior Analytics (UEBA) finding exclusion rule.
Splunk Enterprise Security could later run attacker-controlled Search Processing Language (SPL) commands from the rule with elevated permissions. With this access, the user could cause Splunk Enterprise Security to read stored credentials and modify lookups and knowledge objects.
The vulnerability is possible because the UEBA finding exclusion workflow does not escape user-controlled rule values before using them in generated SPL. For more information see Create a finding exclusion rule using UEBA configuration page ( ) and Users and roles for 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-131215
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- For more information see Create a finding exclusion rule using UEBA configuration page (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/user-and-entity-behavior-analytics/finding-exclusions-in-splunk-enterprise-security/create-a-finding-exclusion-rule-using-ueba-configuration-page) and 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) 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.