Sensitive Information Disclosure in the SHCConfig logging channel in Clustered Deployments in Splunk Enterprise
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-200.
Summary
In Splunk Enterprise versions below 9.4.3, 9.3.5, 9.2.7, and 9.1.10, and Splunk Cloud Platform versions below 9.3.2411.103, 9.3.2408.113, and 9.2.2406.119, the software potentially exposes the search head cluster [splunk.secret](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/9.4/install-splunk-enterprise-securely/deploy-secure-passwords-across-multiple-servers) key. This exposure could happen if you have a Search Head cluster and you configure the Splunk Enterprise `SHCConfig` log channel at the DEBUG logging level in the clustered deployment. <br><br>The vulnerability would require either local access to the log files or administrative access to internal indexes, which by default only the admin role receives. Review roles and capabilities on your instance and restrict internal index access to administrator-level roles. <br><br>See [Define roles on the Splunk platform with capabilities](https://docs.splunk.com/Documentation/Splunk/latest/Security/Rolesandcapabilities), [Deploy a search head cluster](https://help.splunk.com/en/splunk-enterprise/administer/distributed-search/9.4/deploy-search-head-clustering/deploy-a-search-head-cluster), [Deploy secure passwords across multiple servers](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/9.4/install-splunk-enterprise-securely/deploy-secure-passwords-across-multiple-servers) and [Set a security key for the search head cluster](https://help.splunk.com/splunk-enterprise/administer/distributed-search/9.4/configure-search-head-clustering/set-a-security-key-for-the-search-head-cluster#id_2c54937a_736c_47b5_9485_67e9e390acfa__Set_a_security_key_for_the_search_head_cluster) for more information.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Splunk | Splunk Enterprise | 9.4 to before 9.4.3; 9.3 to before 9.3.5; 9.2 to before 9.2.7; 9.1 to before 9.1.10 | 9.4.3, 9.3.5, 9.2.7, 9.1.10 | Patch available | CNA |
| Splunk | Splunk Cloud Platform | 9.3.2411 to before 9.3.2411.103; 9.3.2408 to before 9.3.2408.113; 9.2.2406 to before 9.2.2406.119 | 9.3.2411.103, 9.3.2408.113, 9.2.2406.119 | Patch available | CNA |
- Splunk Enterprise VendorSplunk Affected 9.4 to before 9.4.3; 9.3 to before 9.3.5; 9.2 to before 9.2.7; 9.1 to before 9.1.10 Fixed in 9.4.3, 9.3.5, 9.2.7, 9.1.10 Patch available CNA
- Splunk Cloud Platform VendorSplunk Affected 9.3.2411 to before 9.3.2411.103; 9.3.2408 to before 9.3.2408.113; 9.2.2406 to before 9.2.2406.119 Fixed in 9.3.2411.103, 9.3.2408.113, 9.2.2406.119 Patch available CNA
CPE configurations NVD · 2
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* | 9.1.0 to before 9.1.10; 9.2.0 to before 9.2.7; 9.3.0 to before 9.3.5; 9.4.0 to before 9.4.3 | Vulnerable | Splunk |
| cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:* | 9.2.2406 to before 9.2.2406.119; 9.3.2408 to before 9.3.2408.113; 9.3.2411 to before 9.3.2411.103 | Vulnerable | Splunk |
- cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* Versions 9.1.0 to before 9.1.10; 9.2.0 to before 9.2.7; 9.3.0 to before 9.3.5; 9.4.0 to before 9.4.3 Vulnerable ·Splunk
- cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:* Versions 9.2.2406 to before 9.2.2406.119; 9.3.2408 to before 9.3.2408.113; 9.3.2411 to before 9.3.2411.103 Vulnerable ·Splunk
Remediation
- Fix · CNA Splunk Enterprise (Splunk) Fixed in 9.4.3, 9.3.5, 9.2.7, 9.1.10
- Fix · CNA Splunk Cloud Platform (Splunk) Fixed in 9.3.2411.103, 9.3.2408.113, 9.2.2406.119
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Splunk Enterprise 9.1.10, 9.2.7 and 2 more versions
6 records Highest priority Priority LOW 6 LOW
Other records, highest priority first
- TI-2025-14614 Remote Command Execution through Scripted Input Files in Splunk EnterprisePriority LOW 33
- TI-2025-14615 Denial of Service (DoS) through “User Interface - Views“ configuration page in Splunk EnterprisePriority LOW 32
- TI-2025-14616 Membership State Change in Splunk Search Head Cluster through a Cross-Site Request Forgery (CSRF) in Splunk EnterprisePriority LOW 28
Timeline
- 2026-10-02 Threatist record created from CVE-2025-20325
- 2026-10-03 Alias added: GHSA-58ph-89f9-hmcp
References
More Splunk vulnerabilities
- TI-2026-16444 Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk Enterprise KEVCVSS 3.1CRITICAL 9.8
- TI-2014-00154 The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly… KEVCVSS 3.1HIGH 7.5
- TI-2023-24841 Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing CVSS 3.1HIGH 8.8
- TI-2023-15979 ‘edit_user’ Capability Privilege Escalation CVSS 3.1HIGH 8.8
- TI-2024-30707 Remote Code Execution (RCE) due to insecure session storage configuration in Splunk Enterprise on Windows CVSS 3.1HIGH 8.8
- TI-2022-21345 Reflected Cross-Site Scripting via the radio template in Splunk Enterprise CVSS 3.1HIGH 8.8
Sources
- CVE-2025-20325 · CVE Program
- CVE-2025-20325 · NVD
- FIRST EPSS
- GHSA-58ph-89f9-hmcp · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences