---
id: "CVE-2026-76291"
kind: "vulnerability"
aliases: ["CVE-2026-76291"]
title: "Splunk Enterprise: scheduled searches skip risky-SPL safeguards, letting users alter data"
severity: "high"
cvss: 8.8
epss: 0.00324
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["runtime", "schedule_search-roles", "self-hosted", "splunk-enterprise"]
not_affected_if: ["no-schedule_search-role", "splunk-cloud-unknown"]
published_at: "2026-10-21T23:17:26+00:00"
first_seen_at: "2026-10-23T21:57:29+00:00"
updated_at: "2026-10-24T13:15:54+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-76291", "first_seen_at": "2026-10-23T21:57:29+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-76291", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# Splunk Enterprise: scheduled searches skip risky-SPL safeguards, letting users alter data

Splunk Enterprise's search scheduler does not apply the SPL safeguards for risky commands to scheduled searches. A user with a role holding the schedule_search capability can run risky SPL commands that read or change Splunk data or disrupt the service.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

Check the installed Splunk Enterprise version against the fixed versions. Review authorize.conf and role settings for roles that include schedule_search.

## Fix

Upgrade to 10.4.4, 10.2.8, 10.0.11, or 9.4.16, matching your release branch. Until then, limit schedule_search to roles that need it.

## Timeline

- 2026-10-23T21:57:29+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-76291
- 2026-10-24T13:15:54+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-76291

## From the sources

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 schedule_search 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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_