Skip to content

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

MediumCVSS 6.5 EPSS 0.34%
Published
Updated
Exploit status
No public exploit known

Description

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 products

ProductAffected versionsFixed in
Splunk Enterprise >= 10.4, < 10.4.2 10.4.2
Splunk Enterprise >= 10.2, < 10.2.6 10.2.6
Splunk Enterprise >= 10.0, < 10.0.9 10.0.9
Splunk Enterprise >= 9.4, < 9.4.14 9.4.14
Splunk Secure Gateway >= 3.10, < 3.10.10 3.10.10
Splunk Secure Gateway >= 3.9, < 3.9.24 3.9.24
Splunk Secure Gateway >= 3.8, < 3.8.71 3.8.71
splunk >= 9.4.0, < 9.4.14 9.4.14
splunk >= 10.0.0, < 10.0.9 10.0.9
splunk >= 10.2.0, < 10.2.6 10.2.6
splunk >= 10.4.0, < 10.4.2 10.4.2
Splunk Secure Gateway >= 3.8.0, < 3.8.71 3.8.71
Splunk Secure Gateway >= 3.9.0, < 3.9.24 3.9.24
Splunk Secure Gateway >= 3.10.0, < 3.10.10 3.10.10

References