Skip to content
Threat Brief

← All advisories

CVE-2026-131180

Medium 6.3No known exploitationFix available

SPL Injection through the rename Command in Splunk Enterprise

Record last updated

CVSS score

6.3

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

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

CISA remediation deadline

None

Not in the KEV catalog

Description

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could create and share a dashboard that contains attacker-controlled Search Processing Language (SPL). The SPL could run using the permissions of the user who opens the dashboard. With this access, the user who created the dashboard could expose stored credentials and write data to an index. The vulnerability is possible because Splunk Enterprise does not correctly escape field names in searches that use the rename command. For more information see rename (https://help.splunk.com/en/splunk-enterprise/spl-search-reference/10.4/search-commands/rename) and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) in the Splunk documentation.

Weakness: CWE-116

Patching and mitigation

Patch status
Fix available (source: CVE record (cisco))
Fix documented (source date)
Vendor solution
Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
SplunkSplunk Enterprisefrom 10.0 before 10.0.1210.0.12CVE Program
SplunkSplunk Enterprisefrom 10.2 before 10.2.910.2.9CVE Program
SplunkSplunk Enterprisefrom 10.4 before 10.4.510.4.5CVE Program
SplunkSplunk Enterprisefrom 9.4 before 9.4.179.4.17CVE 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