# CVE-2026-76296: Missing Authorization through Sourcetype Renaming in Splunk Web for Splunk Enterprise


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-6j5x-xq56-rxx3

## What is CVE-2026-76296?

CVE-2026-76296 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, a user who does not hold the "admin" or "power" Splunk roles could create, move, edit, or delete sourcetype renaming configurations that they own in apps that they do not have permission to access.
The vulnerability is possible when Splunk Web is turned on because Splunk Web does not verify the required app permissions before it performs sourcetype renaming operations.
For more information see Rename source types at search time (https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/10.6/configure-source-types/rename-source-types-at-search-time) in the Splunk documentation.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-76296 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76296 is a medium-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-76296 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-76296/ (Markdown: https://insights.sbomify.com/CVE-2026-76296/index.md)
```

## Sources

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

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