Splunk Secure Gateway <3.10.9: Unauthorized Spacebridge key read via REST
CVE-2026-76261 Published on August 19, 2026
Insecure Default Access Control List through the REST API in Splunk Secure Gateway
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.9, 3.9.23, and 3.8.70, a user who does not hold the "admin" or "power" Splunk roles could read Spacebridge asymmetric private keys, which are secrets that compromise affected Spacebridge private-key material stored in the app collection, through the Splunk Secure Gateway App Key Value Store Representational State Transfer (REST) API. The vulnerability is possible on instances upgraded from older Splunk Secure Gateway deployments when the private-key migration remains incomplete, leaving key material in a collection with an insecure default access control list.
Weakness Type
Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. When a resource is given a permissions setting that provides access to a wider range of actors than required, it could lead to the exposure of sensitive information, or the modification of that resource by unintended parties. This is especially dangerous when the resource is related to program configuration, execution or sensitive user data.
Products Associated with CVE-2026-76261
stack.watch emails you whenever new vulnerabilities are published in Splunk or Splunk Secure Gateway. Just hit a watch button to start following.
Affected Versions
Splunk Enterprise:- Version 10.4 and below 10.4.2 is affected.
- Version 10.2 and below 10.2.6 is affected.
- Version 10.0 and below 10.0.9 is affected.
- Version 9.4 and below 9.4.14 is affected.
- Version 3.10 and below 3.10.9 is affected.
- Version 3.9 and below 3.9.23 is affected.
- Version 3.8 and below 3.8.70 is affected.