CVE-2026-76258: The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. in Splunk Splunk Enterprise
Description
CVE-2026-76258 affects multiple versions of Splunk Enterprise and Splunk Secure Gateway. It involves a hard-coded cryptographic key in the Splunk Secure Gateway companion app registration handler, which allows a non-admin or non-power user to register an arbitrary companion app. This can cause mobile user requests, including sensitive tokens, to be forwarded to an attacker-controlled URL, potentially exposing sensitive data. The vulnerability impacts versions prior to specific fixed releases in both Splunk Enterprise and Splunk Secure Gateway.
CVSS v3.1
Score 6.5medium
Affected software
Splunk
Splunk Enterprise
Splunk
Splunk Secure Gateway
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises from the use of a hard-coded cryptographic key in the Splunk Secure Gateway companion app registration handler. It enables users without admin or power roles to register arbitrary companion apps, allowing forwarding of mobile user requests and tokens to attacker-controlled URLs. This flaw affects Splunk Enterprise versions prior to 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions prior to 3.10.10, 3.9.24, and 3.8.71. The vulnerability increases the risk that encrypted data may be recovered by unauthorized parties.
Potential Impact
An attacker with limited privileges (non-admin/non-power user) can exploit this vulnerability to register arbitrary companion apps that forward mobile user requests and tokens to attacker-controlled URLs. This compromises the confidentiality of all relevant data accessible to the affected mobile user. The CVSS score of 6.5 (medium severity) reflects a network attack vector with low complexity and no user interaction required, resulting in high confidentiality impact but no integrity or availability impact.
Mitigation Recommendations
Fixed versions are available for both Splunk Enterprise and Splunk Secure Gateway. Users should upgrade to at least versions 10.4.2, 10.2.6, 10.0.9, or 9.4.14 for Splunk Enterprise, and 3.10.10, 3.9.24, or 3.8.71 for Splunk Secure Gateway. Applying these official fixes will remediate the vulnerability. No additional mitigation steps are indicated in the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- cisco
- Date Reserved
- 2026-08-19T12:02:03.619Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a862250acd9273b49a6fd76
Added to database: 08/19/2026, 21:38:24 UTC
Last enriched: 09/11/2026, 07:18:58 UTC
Last updated: 10/04/2026, 10:04:21 UTC
Views: 43
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.