# CVE-2026-76297: Federated Search Provider State Change through Cross-Site Request Forgery (CSRF) in Splunk Web for Splunk Enterprise


- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-w44q-fq8p-j89w

## What is CVE-2026-76297?

CVE-2026-76297 is a medium-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026. 

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-76297?


## How do I fix CVE-2026-76297?

No fix has been published for CVE-2026-76297 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76297 being exploited?

There is no known exploitation of CVE-2026-76297 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76297 and fix it if it is affected.

What it is: CVE-2026-76297 is a medium-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-76297 in the wild and no public exploit code.

Affected product: Splunk Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76297/ (Markdown: https://insights.sbomify.com/CVE-2026-76297/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76297
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76297
- OSV: https://osv.dev/vulnerability/CVE-2026-76297

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76297/
Summaries are generated and may contain mistakes; the official description above is the record.