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

Published Aug 19, 2026
·
Updated

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

2 affected components
Splunk Splunk Enterprise<10.4.2, <10.2.6, <10.0.9, <9.4.14
Splunk Splunk Secure Gateway<3.10.10, <3.9.24, <3.8.71

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.4.2
  2. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.2.6
  3. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.0.9
  4. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 9.4.14
  5. Upgrade

    Upgrade Splunk Secure Gateway to a version that resolves this vulnerability.

    Fixed in 3.10.10
  6. Upgrade

    Upgrade Splunk Secure Gateway to a version that resolves this vulnerability.

    Fixed in 3.9.24
  7. Upgrade

    Upgrade Splunk Secure Gateway to a version that resolves this vulnerability.

    Fixed in 3.8.71

Event History

Aug 19, 2026
CVE Published
via MITRE·09:34 PM
Data Sourced
via MITRE·09:34 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203