Cross-site request forgery in Splunk Enterprise federated search
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Tampering
- Confidentiality · integrity · availability
- None · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-352.
Summary
Splunk Enterprise versions from 10.4 before 10.4.4, from 10.2 before 10.2.8, from 10.0 before 10.0.11, and from 9.4 before 9.4.16 are affected. The federated provider REST API accepts GET requests for actions that change provider state, which enables cross-site request forgery (CWE-352). An unauthenticated attacker who tricks a user holding the edit_federated_providers capability into making a browser request can turn off all federated search providers, which temporarily stops federated searches from retrieving data from remote datasets.
Written with Claude Haiku 5.5 from the sources below · 2026-10-30
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Splunk | Splunk Enterprise | 10.4 to before 10.4.4; 10.2 to before 10.2.8; 10.0 to before 10.0.11; 9.4 to before 9.4.16 | 10.4.4, 10.2.8, 10.0.11, 9.4.16 | Patch available | CNA |
- Splunk Enterprise VendorSplunk Affected 10.4 to before 10.4.4; 10.2 to before 10.2.8; 10.0 to before 10.0.11; 9.4 to before 9.4.16 Fixed in 10.4.4, 10.2.8, 10.0.11, 9.4.16 Patch available CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* | 9.4.0 to before 9.4.16; 10.0.0 to before 10.0.11; 10.2.0 to before 10.2.8; 10.4.0 to before 10.4.4 | Vulnerable | Splunk |
- cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* Versions 9.4.0 to before 9.4.16; 10.0.0 to before 10.0.11; 10.2.0 to before 10.2.8; 10.4.0 to before 10.4.4 Vulnerable ·Splunk
Remediation
Upgrade Splunk Enterprise to 10.4.4, 10.2.8, 10.0.11, or 9.4.16, depending on the release line in use.
Written with Claude Haiku 5.5 from the sources below · 2026-10-30
- Fix · CNA Splunk Enterprise (Splunk) Fixed in 10.4.4, 10.2.8, 10.0.11, 9.4.16
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Splunk Enterprise 10.0.11, 10.2.8 and 2 more versions
12 records Highest priority Priority MEDIUM 5 MEDIUM, 7 LOW
Other records, highest priority first
- TI-2026-79027 Protection mechanism failure in Splunk EnterprisePriority MEDIUM 49
- TI-2026-79038 Improper neutralization flaws in Splunk Enterprise hardening releasePriority MEDIUM 43
- TI-2026-79025 Improper access control in Splunk EnterprisePriority MEDIUM 43
Timeline
- 2026-10-21 Threatist record created from CVE-2026-76297
- 2026-10-22 Alias added: GHSA-w44q-fq8p-j89w
- 2026-10-28 CISA SSVC decision points changed
- 2026-10-30 CVSS score added · NVD
References
More Splunk vulnerabilities
- TI-2026-16444 Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk Enterprise KEVCVSS 3.1CRITICAL 9.8
- TI-2014-00154 The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly… KEVCVSS 3.1HIGH 7.5
- TI-2023-24841 Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing CVSS 3.1HIGH 8.8
- TI-2023-15979 ‘edit_user’ Capability Privilege Escalation CVSS 3.1HIGH 8.8
- TI-2024-30707 Remote Code Execution (RCE) due to insecure session storage configuration in Splunk Enterprise on Windows CVSS 3.1HIGH 8.8
- TI-2022-21345 Reflected Cross-Site Scripting via the radio template in Splunk Enterprise CVSS 3.1HIGH 8.8
Sources
- CVE-2026-76297 · CVE Program
- CVE-2026-76297 · NVD
- FIRST EPSS
- GHSA-w44q-fq8p-j89w · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences