CVE-2026-76254: SPL Command Safeguards Bypass through Splunk Web in Splunk Enterprise
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, 9.4.14, and 9.3.14, an unauthenticated user could cause another user to dispatch arbitrary Search Processing Language (SPL) pipelines from Dataset Explorer with the same privileges as that user, which can allow for access to all relevant data and system integrity available to that user and affect system availability. The vulnerability is possible because Dataset Explorer does not validate or escape dataset names before building SPL searches and does not apply SPL safeguards for risky commands to those searches. The vulnerability requires the attacker to phish the user by tricking them into opening the crafted link. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Explore a dataset (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/manage-and-explore-datasets/explore-a-dataset) 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
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?
Organizations running affected Splunk Enterprise versions are exposed when a user can be persuaded to open an attacker-crafted link. The impact is limited by the privileges of the user who opens the link, but arbitrary SPL pipelines run with that user's permissions.
What does an attacker need to exploit it?
The attacker does not need to authenticate, but must successfully phish a target user into opening a crafted link. The issue cannot be exploited at will without that user interaction.
Are standard SPL safeguards sufficient to prevent exploitation?
No. The affected Dataset Explorer search construction does not validate or escape dataset names and does not apply SPL safeguards for risky commands to those searches.
Which versions should be remediated?
Upgrade to 10.4.2, 10.2.6, 10.0.9, 9.4.14, or 9.3.14, as applicable to the deployed release branch. Versions below those releases are affected.