dbcve.org
SplunkApplication

CVE-2025-20371

HIGH · 8.8 CVSS v3.1 Published 2025-10-01
Fix available
A fix is available. Upgrade to 9.2.8 / 9.2.2406.122 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 10.0.1, 9.4.4, 9.3.6 and 9.2.8, and Splunk Cloud Platform versions below 9.3.2411.109, 9.3.2408.119 and 9.2.2406.122, an unauthenticated attacker could trigger a blind server-side request forgery (SSRF) potentially letting an attacker perform REST API calls on behalf of an authenticated high-privileged user.

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

An unauthenticated attacker can trigger a blind server-side request forgery (SSRF) in Splunk Enterprise and Cloud Platform, allowing them to force the server to perform REST API calls on behalf of an authenticated high-privileged user.

MitigationUpgrade Splunk Enterprise to version 10.0.1, 9.4.4, 9.3.6, or 9.2.8 (or later), or upgrade Splunk Cloud Platform to version 9.3.2411.109, 9.3.2408.119, or 9.2.2406.122 (or later).

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.2.0, < 9.2.8>= 9.3.0, < 9.3.6>= 9.4.0, < 9.4.4= 10.0.0
Splunk Cloud PlatformApplication
Affected:>= 9.2.2406, < 9.2.2406.122>= 9.3.2408, < 9.3.2408.119>= 9.3.2411, < 9.3.2411.109

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check Splunk Enterprise version
    Run: splunk --version or check $SPLUNK_HOME/etc/splunk.version file
    Affected if Version is 9.2.0-9.2.7, 9.3.0-9.3.5, 9.4.0-9.4.3, or exactly 10.0.0
  2. Check Splunk Cloud Platform version
    Navigate to Settings > System > Server Settings > About Splunk or check Cloud diagnostics
    Affected if Version is 9.2.2406.0 through 9.2.2406.121, 9.3.2408.0 through 9.3.2408.118, or 9.3.2411.0 through 9.3.2411.108
  3. Verify Splunk Web is accessible from untrusted networks
    Check firewall rules and Splunk web.conf for httpport setting; confirm port 8000/443 is exposed externally
    Affected if Splunk Web port is reachable from unauthenticated/untrusted network sources

If your Splunk version falls within the affected ranges and the web interface is network-accessible to unauthenticated users, you are affected by this SSRF vulnerability.

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.2.8 / 9.2.2406.122 / 9.3.6 or later
Fixed in 9.2.89.2.2406.1229.3.6
Interim mitigation

Upgrade Splunk Enterprise to version 10.0.1, 9.4.4, 9.3.6, or 9.2.8 (or later), or upgrade Splunk Cloud Platform to version 9.3.2411.109, 9.3.2408.119, or 9.2.2406.122 (or later).

Recommended fix High confidence

Splunk Enterprise: 9.2.8, 9.3.6, 9.4.4, or 10.0.1 (depending on branch); Splunk Cloud Platform: 9.2.2406.122, 9.3.2408.119, or 9.3.2411.109 (depending on version)

  1. 1. Identify current Splunk Enterprise or Splunk Cloud Platform version by navigating to Settings > About in the Splunk UI or running 'splunk version' from CLI
  2. 2. For Splunk Enterprise: Determine which version branch you are on (9.2.x, 9.3.x, 9.4.x, or 10.0.0)
  3. 3. For Splunk Cloud Platform: Check your current version against the specific build numbers provided in the advisory
  4. 4. Review Splunk upgrade documentation and release notes for your target version
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Create a backup of your Splunk configuration and data
  7. 7. Apply the appropriate upgrade: Splunk Enterprise 9.2.x users upgrade to 9.2.8; 9.3.x to 9.3.6; 9.4.x to 9.4.4; 10.0.0 to 10.0.1; Cloud Platform users upgrade to 9.2.2406.122, 9.3.2408.119, or 9.3.2411.109 respectively
  8. 8. Verify the upgrade was successful and Splunk services are running
Caveat Splunk upgrades typically require careful planning; review release notes for breaking changes between minor versions; test thoroughly in staging before production deployment

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

Fix this in Splunk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20371 — 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-20371 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