CVE-2025-20325

Sensitive Information Disclosure in the SHCConfig logging channel in Clustered Deployments in Splunk Enterprise

MEDIUM
5.3
CVSS Score
Published: July 7, 2025 at 05:48 PM UTC
Updated: June 17, 2026 at 08:41 AM UTC
2 products affected across 1 vendorSplunkSplunk Cloud Platform

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

9.1 ≤ v < 9.1.109.1.0 ≤ v < 9.1.109.2 ≤ v < 9.2.79.2.0 ≤ v < 9.2.79.3 ≤ v < 9.3.59.3.0 ≤ v < 9.3.59.4 ≤ v < 9.4.39.4.0 ≤ v < 9.4.39.19.29.39.4
Affected range stops below 9.1.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.3, so it looks safe — our inference, not a vendor statement
9.2.2406 ≤ v < 9.2.2406.1199.3.2408 ≤ v < 9.3.2408.1139.3.2411 ≤ v < 9.3.2411.1039.2.24069.3.24089.3.2411
Affected range stops below 9.2.2406.119, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2408.113, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2411.103, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-200

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card