CVE-2026-76261: 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.4.2 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.2.6 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.0.9 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 9.4.14 - Upgrade
Upgrade
Splunk Secure Gatewayto a version that resolves this vulnerability.Fixed in 3.10.9 - Upgrade
Upgrade
Splunk Secure Gatewayto a version that resolves this vulnerability.Fixed in 3.9.23 - Upgrade
Upgrade
Splunk Secure Gatewayto a version that resolves this vulnerability.Fixed in 3.8.70
Event History
Frequently Asked Questions
Which deployments are realistically exposed to this issue?
The issue is possible on Splunk instances upgraded from older Splunk Secure Gateway deployments where private-key migration remains incomplete. In that condition, Spacebridge private-key material can remain in an app collection with an insecure default access control list.
What level of access does an attacker need?
An attacker needs an authenticated Splunk user account that does not have the admin or power role. They can use the Splunk Secure Gateway App Key Value Store REST API to read the exposed Spacebridge asymmetric private keys.
How can I determine whether my instance is affected?
Determine whether the instance is running a listed vulnerable Splunk Enterprise or Splunk Secure Gateway version, and whether it was upgraded from an older Secure Gateway deployment with incomplete private-key migration. The vulnerable condition is key material remaining in a collection with an insecure default access control list.