Skip to content
Threat Brief

← All advisories

CVE-2026-131198

High 7.1No known exploitationFix available

SPL Injection through the Mission Control REST API in Splunk Enterprise Security

Record last updated

CVSS score

7.1

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 14% 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 that holds a role with the mc_view_im_data capability could cause the Mission Control incident mapping Representational State Transfer (REST) API to run arbitrary Search Processing Language (SPL) commands with elevated permissions. With this access, the user could expose all data in Splunk indexes and all stored credentials and modify protected indexes and lookup data. The vulnerability is possible because the Mission Control incident mapping REST API does not validate incident identifiers before including them in SPL searches. For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Overview of Mission Control in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/mission-control/overview-of-mission-control-in-splunk-enterprise-security) in the Splunk documentation.

Weakness: CWE-20

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