CVE-2026-131181: Search Processing Language (SPL) Injection in Data Model Acceleration in Splunk Enterprise
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.6.1 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.4.5 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.2.9 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.0.12 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 9.4.17
Event History
Frequently Asked Questions
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.
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.
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.
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.