CVE-2026-131181: Search Processing Language (SPL) Injection in Data Model Acceleration 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.16, a user who does not hold the "admin" or "power" Splunk roles could use Data Model Acceleration to run malicious Search Processing Language (SPL) commands and perform actions through the Representational State Transfer (REST) API that the user cannot perform directly. The vulnerability is possible because Splunk Enterprise does not neutralize user-provided data before it adds that data to a generated search. For more information, see Accelerate data models (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.2/use-data-summaries-to-accelerate-searches/accelerate-data-models), Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and About the search language (https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.6/search-overview/about-the-search-language).

Affected Software

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

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.6.1
  2. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.4.5
  3. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.2.9
  4. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.0.12
  5. Upgrade

    Upgrade Splunk Enterprise 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

Which users could exploit this issue?

A user who does not have the "admin" or "power" Splunk roles could exploit the issue. Exploitation requires that the user can use Data Model Acceleration.

2

What access and conditions are required for exploitation?

The attacker needs network access and valid low-privileged Splunk access; no user interaction is required. The attacker uses malicious input in Data Model Acceleration to inject SPL into a generated search.

3

What could an attacker do after successful exploitation?

An attacker could execute malicious SPL commands and use the REST API to perform actions that their account could not perform directly. The reported impact is integrity compromise and limited availability impact, with no confidentiality impact listed.

4

Which versions should be remediated?

Affected versions are Splunk Enterprise releases below 10.4.5, 10.2.9, 10.0.12, and 9.4.16. Update to the applicable listed release 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