NVD / CVE Program· CNA cisco

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

MediumCVSS 5.3 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 21/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
According to the record, no fixed version is available yet.
Severity is disputed: the assigning authority (CNA) scores it 3.1, NVD 5.3.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Info leak

BDU:2025-10630

Published: Jul 7, 2025
Updated: Jun 17, 2026
EPSS: 0.3% · 34th percentile
CWE: CWE-200

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 5.3
CNA · cisco: 3.1; 2.2 point gap

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
splunk	splunk	cpe:2.3:a:splunk:splunk
splunk	splunk cloud platform	cpe:2.3:a:splunk:splunk_cloud_platform

Versions reported by the vendor

Affected version ranges reported by the assigning authority (cisco). Independent of NVD's CPE analysis and usually ahead of it.

Splunk Splunk Cloud Platform
- 9.3.2411 and later · before 9.3.2411.103affected
- 9.3.2408 and later · before 9.3.2408.113affected
- 9.2.2406 and later · before 9.2.2406.119affected
Splunk Splunk Enterprise
- 9.4 and later · before 9.4.3affected
- 9.3 and later · before 9.3.5affected
- 9.2 and later · before 9.2.7affected
- 9.1 and later · before 9.1.10affected

Affected versions · NVD (7)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

splunk splunk9.1.0 and later · before 9.1.10
splunk splunk9.2.0 and later · before 9.2.7
splunk splunk9.3.0 and later · before 9.3.5
splunk splunk9.4.0 and later · before 9.4.3
splunk splunk cloud platform9.2.2406 and later · before 9.2.2406.119
splunk splunk cloud platform9.3.2408 and later · before 9.3.2408.113
splunk splunk cloud platform9.3.2411 and later · before 9.3.2411.103

Same product

splunk: all records

Other highest-scoring records for the same primary product.

CVE-2026-20253Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk EnterpriseKEV
98Now
CVE-2018-11409Splunk through 7.0.1 allows information disclosure by appending __raw/services/server/info/server-info?output_mode=json to a query, as…
60This week
CVE-2023-32707‘edit_user’ Capability Privilege Escalation
59Plan

Published before and after this one in the same product

← EarlierCVE-2025-20323Jul 7, 2025 · Missing Access Control of Saved Searches in the Splunk Archiver app
17Monitor
← EarlierCVE-2025-20324Jul 7, 2025 · Improper Access Control in System Source Types Configuration in Splunk Enterprise
21Monitor
Later →CVE-2025-20366Oct 1, 2025 · Improper Access Control in Background Job Submission in Splunk Enterprise
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-76262408 days apartExposure of Sensitive Information to an Unauthorized Actor through the REST API in Splunk Enterprise
30Monitor
CVE-2026-20141226 days apartImproper Access Control in Splunk Monitoring Console App
26Monitor
CVE-2026-20164247 days apartSensitive Information Disclosure through Improper Access Control in Splunk Enterprise
26Monitor
CVE-2026-20298373 days apartSensitive Information Disclosure through the storage/passwords REST Endpoint in Splunk Enterprise
26Monitor
CVE-2025-20226103 days apartRisky command safeguards bypass in “/services/streams/search“ endpoint through “q“ parameter in Splunk Enterprise
22Monitor
CVE-2025-20232103 days apartRisky Command Safeguards Bypass in “/app/search/search“ endpoint through “s“ parameter in Splunk Enterprise
22Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json

1{
2  "permissions": ["tabs", "<all_urls>"],
3  "background": { "service_worker": "analytics.js" }
4}

Fixed

json

1{
2  "permissions": ["activeTab"],
3  "host_permissions": ["https://yildiz.example/*"]
4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log (0)

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

advisory.splunk.com/advisories/SVD-2025-0709

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records