CVE-2026-76333: Stored Cross-Site Scripting (XSS) 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 with a crafted Uniform Resource Locator (URL). When another authenticated user selects the stored action from Event Actions and selects Continue, attacker-controlled JavaScript runs in the browser of that user. This could expose data or actions available through Splunk Web to that user. The vulnerability is possible because Dashboard Studio does not sufficiently validate workflow-action URLs before processing them. 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. For more information see 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) in the Splunk documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.4.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.2.6 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.9 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 9.4.14
Event History
Frequently Asked Questions
Who is exposed to this issue?
Splunk Enterprise deployments running versions below 10.4.2, 10.2.6, 10.0.9, or 9.4.14 are affected. Exploitation targets authenticated Splunk Web users who can be persuaded to select a malicious stored workflow action from Event Actions and then select Continue.
What access and user interaction does an attacker need?
The attacker must hold the Splunk "power" role and create a Dashboard Studio workflow action containing a crafted URL. They must also phish an authenticated victim into initiating the browser request; the attacker cannot exploit the issue at will.
What could successful exploitation allow?
Attacker-controlled JavaScript runs in the victim's browser in the Splunk Web context. This can expose data or perform actions available to that authenticated user through Splunk Web.
How can I determine whether my environment needs remediation?
Check the installed Splunk Enterprise version against the fixed versions: 10.4.2, 10.2.6, 10.0.9, and 9.4.14. Also review Dashboard Studio workflow actions created by users with the "power" role for crafted or unexpected URLs.