Use of Hard-coded Cryptographic Key through Companion App Registration in Splunk Secure Gateway

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 (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.

Timeline

1. Aug 19, 2026, 9:34 PM UTCCVE published
2. Aug 26, 2026, 2:49 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Aug 26, 2026, 3:23 PM UTCRecord last updated

Affected versions

• Splunk Splunk Enterprise

  From 10.4 · fixed in 10.4.2; From 10.2 · fixed in 10.2.6; From 10.0 · fixed in 10.0.9; From 9.4 · fixed in 9.4.14

• Splunk Splunk Secure Gateway

  From 3.10 · fixed in 3.10.10; From 3.9 · fixed in 3.9.24; From 3.8 · fixed in 3.8.71

References 1