# CVE-2026-76292: Missing Authorization through REST API Endpoints in Splunk Secure Gateway


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-42f3-xxmj-h2v2

## What is CVE-2026-76292?

CVE-2026-76292 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, and Splunk Secure Gateway versions below 3.10.12, 3.9.26, and 3.8.73, a low-privileged user that does not hold the "admin" Splunk role or the "sc_admin" Splunk Secure Gateway role could read mobile alert notification data for other users through Splunk Secure Gateway App Key Value Store (KV Store) Representational State Transfer (REST) API endpoints.
The vulnerability is possible because the affected Splunk Secure Gateway App Key Value Store collections do not enforce user-level authorization for read requests.
For more information see About the app key value store (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/administer-the-app-key-value-store/about-the-app-key-value-store) and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-76292 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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