Medium [CVE-2026-76258] Use of Hard-coded Cryptographic Key through Companion App Registration in Splunk Secure Gateway
This medium-severity Splunk advisory covers CVE-2026-76258 affecting Splunk Enterprise, Splunk Secure Gateway.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published
Android app · Google Play
Monitor future Splunk CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
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.10, 3.9.24, and 3.8.71, a user who does not hold the "admin" or "power" Splunk roles could register an arbitrary companion app and cause Splunk Secure Gateway to forward mobile user requests, including tokens that compromise all relevant data available to the affected mobile user, to an attacker-controlled Uniform Resource Locator (URL).
The vulnerability is possible because a hard-coded cryptographic key in the Splunk Secure Gateway companion app registration handler allows for arbitrary callback URL registration without restriction. For more information see Define roles on the Splunk platform with capabilities ( ) in the Splunk documentation.
- Splunk Enterprise 10.4 before 10.4.2
- Splunk Enterprise 10.2 before 10.2.6
- Splunk Enterprise 10.0 before 10.0.9
- Splunk Enterprise 9.4 before 9.4.14
- Splunk Secure Gateway 3.10 before 3.10.10
- Splunk Secure Gateway 3.9 before 3.9.24
- Splunk Secure Gateway 3.8 before 3.8.71
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
- 10.4.2
- 10.2.6
- 10.0.9
- 9.4.14
- 3.10.10
- 3.9.24
- 3.8.71
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Mitigation
Upgrade to a fixed release: 10.4.2, 10.2.6, 10.0.9, 9.4.14, 3.10.10, 3.9.24. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.