dbcve.org
SplunkApplication

CVE-2025-20325

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-07
Fix available
A fix is available. Upgrade to 9.1.10 / 9.2.7 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Splunk Enterprise versions below 9.4.3, 9.3.5, 9.2.7, and 9.1.10 (and specific Splunk Cloud versions), the SHCConfig log channel configured at DEBUG level in search head cluster deployments can expose the splunk.secret key used for search head cluster authentication. An attacker with local access to log files or administrative access to internal indexes could obtain this secret.

MitigationDisable DEBUG logging for the SHCConfig log channel in clustered deployments and restrict access to internal indexes to administrator-level roles only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SplunkApplication
Affected:>= 9.1.0, < 9.1.10>= 9.2.0, < 9.2.7>= 9.3.0, < 9.3.5>= 9.4.0, < 9.4.3
Splunk Cloud PlatformApplication
Affected:>= 9.2.2406, < 9.2.2406.119>= 9.3.2408, < 9.3.2408.113>= 9.3.2411, < 9.3.2411.103

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Search Head Cluster deployment
    Run the command: splunk list cluster-config -auth <admin:password> and look for 'shc' in the output, or check for $SPLUNK_HOME/etc/system/default/serverclass.conf with shc_cluster configuration
    Affected if The system is NOT a Search Head Cluster (the vulnerability only affects SHC deployments)
  2. Check SHCConfig log level configuration
    Inspect $SPLUNK_HOME/etc/system/local/inputs.conf for a [shcconfig] stanza and verify if the loglevel is set to DEBUG, or run: splunk cmd python $SPLUNK_HOME/bin/scripts/shcconfig_logging.py --check
    Affected if The SHCConfig channel is set to DEBUG level (vulnerability requires DEBUG logging)
  3. Inspect log files for splunk.secret exposure
    Search log files in $SPLUNK_HOME/var/log/splunk/ for the string 'splunk.secret' using: grep -r 'splunk.secret' $SPLUNK_HOME/var/log/splunk/ | head -20
    Affected if The literal string 'splunk.secret' appears in any log files (confirms active exploitation or vulnerable configuration)
  4. Verify installed Splunk version
    Run: splunk version or check $SPLUNK_HOME/etc/splunk.version for the full version string
    Affected if The installed version falls within any of these ranges: 9.1.0 to 9.1.9, 9.2.0 to 9.2.6, 9.3.0 to 9.3.4, 9.4.0 to 9.4.2 (or Cloud versions 9.2.2406 to 9.2.2406.118, 9.3.2408 to 9.3.2408.112, 9.3.2411 to 9.3.2411.102)

A user is affected if they run a vulnerable Splunk version AND operate a Search Head Cluster with SHCConfig logging set to DEBUG level, allowing potential exposure of the splunk.secret key in log files or internal indexes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.1.10 / 9.2.7 / 9.2.2406.119 or later
Fixed in 9.1.109.2.79.2.2406.119
Interim mitigation

Disable DEBUG logging for the SHCConfig log channel in clustered deployments and restrict access to internal indexes to administrator-level roles only.

Recommended fix High confidence

Splunk Enterprise: 9.1.10, 9.2.7, 9.3.5, or 9.4.3 (choose the appropriate version based on current branch); Splunk Cloud Platform: 9.2.2406.119, 9.3.2408.113, or 9.3.2411.103

  1. 1. Identify the current Splunk Enterprise or Splunk Cloud Platform version in use.
  2. 2. For Splunk Enterprise: If running 9.1.x, upgrade to 9.1.10 or later. If running 9.2.x, upgrade to 9.2.7 or later. If running 9.3.x, upgrade to 9.3.5 or later. If running 9.4.x, upgrade to 9.4.3 or later.
  3. 3. For Splunk Cloud Platform: If running 9.2.2406.x, upgrade to 9.2.2406.119 or later. If running 9.3.2408.x, upgrade to 9.3.2408.113 or later. If running 9.3.2411.x, upgrade to 9.3.2411.103 or later.
  4. 4. Follow standard Splunk upgrade procedures including backing up configuration files and testing in a non-production environment first.
  5. 5. After upgrade, verify that the SHCConfig log channel is not set to DEBUG level in production environments as a hardening measure.
Caveat Review Splunk upgrade documentation for version-specific migration considerations; ensure compatibility with existing apps and custom configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Splunk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20325 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data