CVE-2026-76258: 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.
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.10 - Upgrade
Upgrade
Splunk Secure Gatewayto a version that resolves this vulnerability.Fixed in 3.9.24 - Upgrade
Upgrade
Splunk Secure Gatewayto a version that resolves this vulnerability.Fixed in 3.8.71
Event History
Frequently Asked Questions
Who can exploit this issue?
A Splunk user who does not hold the "admin" or "power" roles can exploit it by registering an arbitrary companion app. Exploitation does not require user interaction.
What could an attacker obtain?
Splunk Secure Gateway can forward affected mobile users' requests to an attacker-controlled URL, including tokens. Those tokens can compromise all relevant data available to the affected mobile user.
Which deployments need remediation?
Affected deployments include Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, together with Splunk Secure Gateway versions below 3.10.10, 3.9.24, and 3.8.71.
What condition enables the attack?
The issue depends on the ability to register a companion app with an arbitrary callback URL. The registration handler permits this because it uses a hard-coded cryptographic key and does not restrict callback URLs.