Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-76292 Overview
CVE-2026-76292 is a missing authorization vulnerability [CWE-862] in Splunk Enterprise and Splunk Secure Gateway. A low-privileged authenticated user who does not hold the admin Splunk role or the sc_admin Splunk Secure Gateway role can read mobile alert notification data belonging to other users. The flaw resides in the Splunk Secure Gateway App Key Value Store (KV Store) Representational State Transfer (REST) API endpoints, which fail to enforce user-level authorization on read requests. Splunk published advisory SVD-2026-1007 describing the issue and the fixed versions.
Critical Impact
Any authenticated Splunk user can read other users' mobile alert notification data through unauthorized KV Store REST API queries.
Affected Products
- Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16
- Splunk Secure Gateway versions below 3.10.12, 3.9.26, and 3.8.73
- Deployments exposing the Splunk Secure Gateway App KV Store collections to non-admin users
Discovery Timeline
- 2026-10-21 - CVE-2026-76292 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-76292
Vulnerability Analysis
The Splunk Secure Gateway app stores mobile alert notification data in App Key Value Store (KV Store) collections. The KV Store is exposed through REST API endpoints that return documents to authenticated callers. In vulnerable builds, the Secure Gateway collections do not scope results to the requesting user. A caller with any valid Splunk role can issue read requests against these collections and receive notification records authored for or addressed to other users. The information disclosed can include notification payloads tied to alerts configured by higher-privileged accounts, enabling reconnaissance of monitored systems and alert conditions.
Root Cause
The affected KV Store collections omit user-level authorization checks on read operations. Splunk roles such as admin and sc_admin are intended to govern access to Secure Gateway data, but the collections do not evaluate role membership or ownership of individual documents when serving GET requests. This is a classic missing authorization pattern [CWE-862] where authentication is enforced but authorization is not.
Attack Vector
Exploitation requires network access to the Splunk management interface and valid credentials for a low-privileged Splunk account. The attacker issues REST API requests to the Splunk Secure Gateway KV Store endpoints and reads returned documents. No user interaction, elevated privileges, or specialized tooling is required. Refer to the Splunk Security Advisory SVD-2026-1007 for endpoint specifics and the About the app key value store documentation for background on KV Store REST semantics.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-76292
Indicators of Compromise
- REST API requests to Splunk Secure Gateway KV Store collection endpoints originating from non-admin user sessions
- Unusually broad or repeated GET requests against /servicesNS/-/splunk_secure_gateway/storage/collections/data/ paths by low-privileged accounts
- Access patterns where a single user retrieves notification records associated with multiple other users
Detection Strategies
- Review Splunk _internal audit and REST logs for Secure Gateway KV Store reads correlated with the authenticated user's role
- Alert on KV Store queries where the result set references user fields that do not match the requesting principal
- Baseline normal Secure Gateway API usage per role and flag deviations from low-privileged accounts
Monitoring Recommendations
- Enable and retain Splunk REST API audit logging for the splunk_secure_gateway app
- Forward Splunk audit events to a centralized analytics platform for cross-user correlation
- Periodically review role assignments to confirm that sc_admin membership is limited to intended administrators
How to Mitigate CVE-2026-76292
Immediate Actions Required
- Upgrade Splunk Enterprise to 10.4.4, 10.2.8, 10.0.11, or 9.4.16 or later within the respective maintenance branch
- Upgrade Splunk Secure Gateway to 3.10.12, 3.9.26, or 3.8.73 or later
- Audit existing Splunk roles and remove unnecessary low-privileged accounts with access to the Splunk management port
Patch Information
Splunk addressed the missing authorization check in the Splunk Secure Gateway App KV Store collections. Fixed releases are documented in Splunk Security Advisory SVD-2026-1007. Apply the patched Secure Gateway app version that corresponds to your Splunk Enterprise release branch.
Workarounds
- Disable or uninstall the Splunk Secure Gateway app if mobile alerting is not in use, per guidance in the vendor advisory
- Restrict network access to the Splunk management interface so only trusted administrative hosts can reach REST endpoints
- Review and tighten role-based access control following the About configuring role-based user access documentation
# Configuration example
# Verify installed Splunk Secure Gateway version
$SPLUNK_HOME/bin/splunk display app splunk_secure_gateway
# Disable the Secure Gateway app if mobile alerting is not required
$SPLUNK_HOME/bin/splunk disable app splunk_secure_gateway -auth admin:<password>
$SPLUNK_HOME/bin/splunk restart
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

