CVE-2026-76291: Improper Access Control through Scheduled Search Safeguards in Splunk Enterprise
In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the schedulesearch capability could bypass the expected safeguards in the scheduled search workflow. The user could then run risky Search Processing Language (SPL) commands that disclose or alter Splunk Enterprise data or disrupt Splunk Enterprise availability. The vulnerability is possible because the Splunk Enterprise search scheduler does not apply SPL safeguards for risky commands to scheduled searches. For more information see SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) in the Splunk documentation. For more information see authorize.conf (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.6/configuration-file-reference/10.6.0-configuration-file-reference/authorize.conf) 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.4 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.2.8 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.0.11 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 9.4.16
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated Splunk Enterprise user whose role has the schedule_search capability can exploit it. The attack can be performed remotely and does not require user interaction.
Which deployments are affected?
Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 are affected. The issue is relevant where the schedule_search capability is assigned to user roles.
What could an attacker do after exploitation?
The user could run risky SPL commands through scheduled searches despite the expected safeguards. This could disclose or alter Splunk Enterprise data, or disrupt availability.
What can be done before upgrading?
Review roles assigned the schedule_search capability and remove that capability from users who do not require scheduled-search functionality. Restricting this capability limits which users can use the affected workflow.