CVE-2026-76261 Insecure Default Access Control List through the REST API in Splunk Secure Gateway

Medium 5.3 Published 19 Aug 2026 Updated 26 Aug 2026

Non-admin users can read private keys via REST API if key migration is incomplete, exposing sensitive secrets in Splunk Secure Gateway.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

What is CVE-2026-76261?

CVE-2026-76261 is a medium-severity missing authorization vulnerability in Splunk Splunk, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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: CWE-732

Which versions are affected by CVE-2026-76261?

It affects 2 products.

Products include Splunk Splunk, Splunk Splunk Secure Gateway.

How do I fix CVE-2026-76261?

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

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-76261 being exploited?

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

All Splunk Splunk vulnerabilities

Sources

Also known as GHSA-58cf-vcvf-5vh5.