AI Threat AlertCVE-2026-76297: Splunk Enterprise: CSRF via GET disables federated search
MEDIUMSplunk Enterprise has a cross-site request forgery flaw in its federated provider REST API, which accepts state-changing GET requests. An attacker who phishes a user holding the edit_federated_providers capability can get that user's browser to switch off all federated search providers, temporarily cutting off searches against remote Splunk datasets. Risk is low: CVSS is 4.2, exploitation needs a high-complexity phish and a privileged victim, and there is no KEV listing, public exploit, or Nuclei template, and no EPSS score is available. The AI/ML link is indirect: it matters only where Splunk data feeds ML pipelines, model monitoring, or AI security analytics. Upgrade to 10.4.4, 10.2.8, 10.0.11, or 9.4.16 or later per Splunk advisory SVD-2026-1007, and limit the edit_federated_providers capability to as few roles as possible.
What is the risk?
Low to medium overall (CVSS 3.1: 4.2). The attack is network-based but needs high complexity and user interaction, because a privileged user must be phished into triggering a crafted request. Confidentiality is unaffected. Integrity and availability impact are low, limited to disabling federated providers temporarily. No known exploitation, public exploit, or KEV listing. Exposure is limited to organizations that use federated search and have users holding edit_federated_providers.
How does the attack unfold?
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade Splunk Enterprise to 10.4.4, 10.2.8, 10.0.11, 9.4.16 or later, as per advisory SVD-2026-1007. 2) Restrict the edit_federated_providers capability to the minimum number of administrative roles. 3) Train privileged users to avoid clicking untrusted links while logged in to Splunk Web, and use separate browser sessions or profiles for admin work. 4) Monitor audit logs for unexpected GET requests that change federated provider state, and alert when providers are disabled outside change windows. 5) Add a health check or alert for federated search failures or empty results from remote datasets.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-76297?
Splunk Enterprise has a cross-site request forgery flaw in its federated provider REST API, which accepts state-changing GET requests. An attacker who phishes a user holding the edit_federated_providers capability can get that user's browser to switch off all federated search providers, temporarily cutting off searches against remote Splunk datasets. Risk is low: CVSS is 4.2, exploitation needs a high-complexity phish and a privileged victim, and there is no KEV listing, public exploit, or Nuclei template, and no EPSS score is available. The AI/ML link is indirect: it matters only where Splunk data feeds ML pipelines, model monitoring, or AI security analytics. Upgrade to 10.4.4, 10.2.8, 10.0.11, or 9.4.16 or later per Splunk advisory SVD-2026-1007, and limit the edit_federated_providers capability to as few roles as possible.
Is CVE-2026-76297 actively exploited?
No confirmed active exploitation of CVE-2026-76297 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-76297?
1) Upgrade Splunk Enterprise to 10.4.4, 10.2.8, 10.0.11, 9.4.16 or later, as per advisory SVD-2026-1007. 2) Restrict the edit_federated_providers capability to the minimum number of administrative roles. 3) Train privileged users to avoid clicking untrusted links while logged in to Splunk Web, and use separate browser sessions or profiles for admin work. 4) Monitor audit logs for unexpected GET requests that change federated provider state, and alert when providers are disabled outside change windows. 5) Add a health check or alert for federated search failures or empty results from remote datasets.
What systems are affected by CVE-2026-76297?
This vulnerability affects the following AI/ML architecture patterns: Security monitoring and SIEM pipelines, ML observability and telemetry aggregation, Federated log analytics for AI systems.
What is the CVSS score for CVE-2026-76297?
CVE-2026-76297 has a CVSS v3.1 base score of 5.4 (MEDIUM). The EPSS exploitation probability is 0.11%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0011.003Malicious LinkAML.T0052PhishingCompliance Controls Affected
What are the technical details?
Original Advisory
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.
Exploitation Scenario
An attacker sends a targeted phishing email or message to a Splunk administrator holding edit_federated_providers, with a link or embedded image that triggers the vulnerable GET endpoint. While logged in to Splunk Web, the admin's browser fires the request, and all federated providers are turned off. Dashboards and scheduled searches that pull ML pipeline telemetry or AI system logs from remote Splunk deployments then fail or return incomplete data, creating a temporary blind spot the attacker could use to carry out other activity with reduced detection.
Weaknesses (CWE)
CWE-352 — Cross-Site Request Forgery (CSRF): The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
- [Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
- [Implementation] Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:LTimeline
Related Vulnerabilities
CVE-2026-3366010.0TensorFlow: type confusion NPD in tensor conversion
Same attack type: DoSCVE-2026-274959.9n8n: Code Injection enables RCE
Same attack type: Social EngineeringCVE-2026-275779.9n8n: Code Injection enables RCE
Same attack type: Social EngineeringCVE-2022-359399.8TensorFlow: ScatterNd OOB write enables RCE/crash
Same attack type: DoSCVE-2022-235879.8TensorFlow: integer overflow in Grappler enables RCE
Same attack type: DoS