# CVE-2026-76263: Improper Access Control through the REST API in Splunk Enterprise

> Unauthorized users can delete other users' SPL2 modules via the REST API due to missing ownership checks in Splunk Enterprise.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-826f-fgv2-26mm

## What is CVE-2026-76263?

CVE-2026-76263 is a medium-severity missing authorization vulnerability in Splunk Splunk, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Splunk Enterprise versions below 10.4.2 and 10.2.6, a user who does not hold the "admin" or "power" Splunk roles could delete Splunk Processing Language version 2 (SPL2) modules belonging to other users through the data management orchestrator interface. The vulnerability does not affect Splunk Enterprise versions below 10.2. The broken object level authorization is possible because the data management orchestrator does not verify that the requesting user owns the target resources before it deletes the modules. For more information see Manage SPL2-based apps (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/meet-splunk-apps/manage-spl2-based-apps) in the Splunk documentation.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Splunk Splunk.

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

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

## Is CVE-2026-76263 being exploited?

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

## Other vulnerabilities in Splunk Splunk

- [CVE-2026-20253](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-76268](https://insights.sbomify.com/CVE-2026-76268/): Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise (critical 9.8)
- [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8)
- [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8)
- [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76263 is a medium-severity missing authorization vulnerability in Splunk Splunk, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76263 in the wild and no public exploit code.

Affected product: Splunk Splunk. 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-76263/ (Markdown: https://insights.sbomify.com/CVE-2026-76263/index.md)
```

## Sources

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

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