Splunk Secure Gateway <10.4.2: Hardcoded Key Allows Arbitrary Callback URL
CVE-2026-76258 Published on August 19, 2026
Use of Hard-coded Cryptographic Key through Companion App Registration 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.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 (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.
Weakness Type
Use of Hard-coded Cryptographic Key
The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.
Products Associated with CVE-2026-76258
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.10 is affected.
- Version 3.9 and below 3.9.24 is affected.
- Version 3.8 and below 3.8.71 is affected.