vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2025-20370

Denial of Service (DoS) through Multiple LDAP Bind Requests in Splunk Enterprise

MEDIUM
4.9
CVSS Score
Published: October 1, 2025 at 04:07 PM UTC
Updated: October 18, 2026 at 09:10 PM UTC
3 products affected across 1 vendorSplunkSplunk Cloud PlatformSplunk Enterprise Cloud

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
Start FreeSign In
Severity
MEDIUM4.9
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

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.108, 9.3.2408.118 and 9.2.2406.123, a user who holds a role that contains the high-privilege capability `change_authentication`, could send multiple LDAP bind requests to a specific internal endpoint, resulting in high server CPU usage, which could potentially lead to a denial of service (DoS) until the Splunk Enterprise instance is restarted. See https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.0/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities and https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.0/use-ldap-as-an-authentication-scheme/configure-ldap-with-splunk-web#cfe47e31_007f_460d_8b3d_8505ffc3f0dd__Configure_LDAP_with_Splunk_Web for more information.

Affected

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

Splunk· Splunk
95%
9.2.0 ≤ v < 9.2.89.3.0 ≤ v < 9.3.69.4.0 ≤ v < 9.4.410.010.0.09.29.2.24069.39.3.24089.3.24119.4
Affected range stops below 10.0.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.2406.123, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2408.118, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2411.108, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.4, so it looks safe — our inference, not a vendor statement
Splunk Cloud Platform· Splunk
95%
9.2.2406 ≤ v < 9.2.2406.1239.3.2408 ≤ v < 9.3.2408.1189.3.2411 ≤ v < 9.3.2411.1089.2.24069.3.24089.3.2411
Affected range stops below 9.2.2406.123, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2408.118, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2411.108, so it looks safe — our inference, not a vendor statement
Splunk Enterprise Cloud· Splunk
90%
9.2.2406 ≤ v < 9.2.2406.1239.3.2408 ≤ v < 9.3.2408.1189.3.2411 ≤ v < 9.3.2411.108

Remediation

No guide yet

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

Patch and advisory references

References (1)

Vendor Advisory
Source: cverecord
https://advisory.splunk.com/advisories/SVD-2025-1005

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

4.9MEDIUMcisco
Vector?

Quick Info

StatusANALYZED
CWE
CWE-400CWE-770

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.

Create accountSign in
Free plan, no card