CVE-2026-76334: SPL Injection through Dashboard Studio Workflow Actions in Splunk Enterprise
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store a Dashboard Studio workflow action containing attacker-controlled Search Processing Language (SPL). When another authenticated user selects the action from Event Actions and selects Continue, Splunk Enterprise runs the injected SPL using the permissions of that user. The injected SPL could access or modify data available to that user. The vulnerability is possible because Dashboard Studio does not sufficiently validate workflow-action URLs before submitting requests. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The user who holds the "power" Splunk role should not be able to exploit the vulnerability at will.
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.4.2 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.2.6 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.0.9 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 9.4.14
Event History
Frequently Asked Questions
Who is exposed to this issue?
Authenticated Splunk Enterprise users who can select Dashboard Studio Event Actions and are induced to select Continue are exposed. The impact is limited to data and actions that the affected user is permitted to access or modify.
What does an attacker need to exploit it?
An attacker needs a Splunk account with the "power" role to save a Dashboard Studio workflow action containing attacker-controlled SPL. They must then phish another authenticated user into initiating the action in that user's browser and selecting Continue.
Are users with the "power" role able to trigger the issue directly?
No. The provided information states that a user holding the "power" role should not be able to exploit the vulnerability at will; exploitation depends on convincing another authenticated user to initiate the request.
Which Splunk Enterprise versions are affected?
Versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14 are affected.