Federated Search Provider State Change through Cross-Site Request Forgery (CSRF) in Splunk Web for Splunk Enterprise

Summary

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could trick a user that holds a role with the edit_federated_providers capability into turning off all federated search providers. Successful exploitation could temporarily prevent federated searches from retrieving data from remote datasets. The vulnerability is possible because the federated provider Representational State Transfer (REST) API accepts GET requests for actions that change provider state. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Run federated searches over remote Splunk platform deployments (https://help.splunk.com/en/splunk-enterprise/search/federated-search/10.6/run-federated-searches-across-other-splunk-deployments/run-federated-searches-over-remote-splunk-platform-deployments) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.

Timeline

1. Oct 21, 2026, 10:51 PM UTCCVE published
2. Oct 22, 2026, 3:26 AM UTCFirst seen by cve.now
3. Oct 28, 2026, 2:03 AM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

4. Oct 28, 2026, 2:03 AM UTCRecord last updated

Affected versions

• Splunk Splunk Enterprise

  From 10.4 · fixed in 10.4.4; From 10.2 · fixed in 10.2.8; From 10.0 · fixed in 10.0.11; From 9.4 · fixed in 9.4.16

References 1