CVE-2026-131180: SPL Injection through the rename Command in Splunk Enterprise

Published Nov 19, 2026
·
Updated

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.

Affected Software

1 affected component
Splunk Splunk Enterprise<10.4.5, <10.2.9, <10.0.12, <9.4.17

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.6.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.4.5
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.2.9
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.12
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.4.17

Event History

Nov 19, 2026
CVE Published
via MITRE·07:55 PM
Data Sourced
via MITRE·07:55 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue, and who is at risk?

A user with the Splunk "power" role can create and share a malicious dashboard. Any user who opens that dashboard may have SPL executed with their own permissions.

2

What could an attacker gain through a malicious dashboard?

The dashboard creator could expose stored credentials available to the user opening the dashboard and write data to an index using that user's access.

3

Are all Splunk Enterprise deployments affected by default?

Exploitation requires a power-role user to be able to create and share a dashboard, and another user to open it. The affected search path involves field names used with the rename command.

4

Which versions require remediation?

Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 are affected. Upgrade to the applicable listed version or later.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203