Skip to content
Threat Brief

← All advisories

CVE-2026-131200

High 8.1No known exploitationFix available

Privilege Escalation through Threat Matching Searches in Splunk Enterprise Security

Record last updated

CVSS score

8.1

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 16% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could create an attacker-controlled saved search. Threat intelligence lookup generation could later run the saved search with elevated permissions, which could let the user who created the saved search run arbitrary Search Processing Language (SPL) commands with those permissions. The vulnerability is possible because Splunk Enterprise Security does not restrict threat intelligence lookup generation to the intended saved searches. For more information see 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) and Turn on threat matching searches in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.0/threat-intelligence/turn-on-threat-matching-searches-in-splunk-enterprise-security) in the Splunk documentation.

Weakness: CWE-863

Patching and mitigation

Patch status
Fix available (source: CVE record (cisco))
Fix documented (source date)
Vendor solution
Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher.
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
SplunkSplunk Enterprise Securityall versions before 8.7.08.7.0CVE Program

Timeline

  1. Disclosure

    CVE record published by cisco

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (cisco)

    Source: CVE record (cisco) (opens in a new tab)

Vendor guidance and references