CVE-2025-20325 | Sensitive Information Disclosure in the SHCConfig logging channel in Clustered Deployments in Splunk Enterprise

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.

Published: 2025-07-07 Last update: 2025-08-01 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-20325 is rated Low Risk (26.6/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.19%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-20325

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-03 0.05% 0.19% +0.13%
2 2026-03-23 0.03% 0.05% +0.03%
3 2025-12-03 0.03%

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-20325

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.1 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
1.6 1.4 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
1.6 3.6 [email protected]

Weakness enumeration for CVE-2025-20325

Affected software / configurations for CVE-2025-20325

Vendor Product Version Raw CPE
splunk splunk >= 9.1.0, < 9.1.10 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk >= 9.2.0, < 9.2.7 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk >= 9.3.0, < 9.3.5 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk >= 9.4.0, < 9.4.3 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk_cloud_platform >= 9.2.2406, < 9.2.2406.119 cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*
splunk splunk_cloud_platform >= 9.3.2408, < 9.3.2408.113 cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*
splunk splunk_cloud_platform >= 9.3.2411, < 9.3.2411.103 cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*

References for CVE-2025-20325

cvelogic Threat Intelligence