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.
Metrics
Affected Vendors & Products
| Vendors | Products |
|---|---|
| Splunk |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
References
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-0801 |
|
History
Thu, 20 Aug 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Splunk splunk
|
|
| CPEs | cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:* |
|
| Vendors & Products |
Splunk splunk
|
Wed, 19 Aug 2026 23:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Splunk
Splunk splunk Enterprise Splunk splunk Secure Gateway |
|
| Vendors & Products |
Splunk
Splunk splunk Enterprise Splunk splunk Secure Gateway |
Wed, 19 Aug 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Use of Hard-coded Cryptographic Key through Companion App Registration in Splunk Secure Gateway | |
| Weaknesses | CWE-321 | |
| References |
| |
| Metrics |
cvssV3_1
|
MITRE
Status: PUBLISHED
Assigner: cisco
Published: 2026-08-19T21:34:16.596Z
Updated: 2026-08-19T21:34:16.596Z
Reserved: 2026-08-19T12:02:03.619Z
Link: CVE-2026-76258
Vulnrichment
No data.
NVD
Status : Analyzed
Published: 2026-08-19T22:17:13.793
Modified: 2026-08-20T14:53:07.723
Link: CVE-2026-76258
Redhat
No data.