CVE-2026-131215
Last modified
CVE-2026-131215 is a high-severity vulnerability rated 8.3/10 on the CVSS scale. 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. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
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 (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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Splunk | Splunk Enterprise Security | < 8.7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-131215?
How severe is CVE-2026-131215?
How do I fix CVE-2026-131215?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-13121Parallels RAS Client RDP Backend Service Exposed Dangerous F…7.8
- CVE-2026-131210In Splunk Enterprise Security versions below 8.7.0, a user t…8.1
- CVE-2026-131211In Splunk App for Payment Card Industry Compliance versions …7.3
- CVE-2026-131212In Splunk Enterprise Security versions below 8.7.0, a user t…4.6
- CVE-2026-131213In Splunk Enterprise Security versions below 8.7.0, a user w…6.7
- CVE-2026-131214In Splunk Enterprise Security versions below 8.7.0, a user t…4.8
- CVE-2026-131216In Splunk Enterprise Security versions below 8.7.0, a user t…5.7
- CVE-2026-131217In Splunk Enterprise Security versions below 8.7.0, a user t…4.6
- CVE-2026-131218In Splunk Enterprise Security versions below 8.7.0, a user t…8.3
- CVE-2026-131219In Splunk Enterprise Security versions below 8.7.0, a user t…3.7
- CVE-2026-13122OpenVPN version 2.6.0 through 2.6.20 and 2.7_alpha1 through …5.3
- CVE-2026-131220In Splunk Enterprise Security versions below 8.7.0, a user w…5.9
Are you affected by CVE-2026-131215?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
