CVE-2026-76261: In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below…
CVE-2026-76261 · Severity: medium · CVSS 5.3 · Published 2026-08-19
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.
No. Junglewise Threat Intelligence has no report of CVE-2026-76261 being exploited in the wild.
How severe is CVE-2026-76261?
Medium severity, with a CVSS score of 5.3, published 19 August 2026.
Which products and versions are affected?
Splunk, Splunk Secure Gateway. The advisory does not name versions.
Is there a fix for CVE-2026-76261?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-76261?
Check whether you run Splunk or Splunk Secure Gateway. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.