Skip to content
Medium 6.3

SPL Injection through the rename Command in Splunk Enterprise

CVE-2026-131180 First seen on SecPulse

Summary

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 t...

Affected packages

PackageAffected → Fixed
SplunkSplunk Enterprise
≥ 10.4, < 10.4.5→ 10.4.5
≥ 10.2, < 10.2.9→ 10.2.9
≥ 10.0, < 10.0.12→ 10.0.12
≥ 9.4, < 9.4.17→ 9.4.17
Original description The description as published by the source.

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.

Source: CVE.org (CVE Program・cvelistV5) NVD

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details