Service interruption via repeated LDAP bind requests
Published Oct 1, 2025 · Updated Oct 1, 2025
Resource exhaustion in Splunk Web in Splunk Enterprise and Enterprise Cloud allows remote authenticated users to interrupt service. Splunk Web accepts repeated LDAP bind requests at an internal endpoint without limiting their aggregate CPU consumption. A role containing the high-privilege change_authentication capability and enabled Splunk Web are required; exploitation drives CPU high until the instance is restarted.
Summary
What happened
Resource exhaustion in Splunk Web in Splunk Enterprise and Enterprise Cloud allows remote authenticated users to interrupt service. Splunk Web accepts repeated LDAP bind requests at an internal endpoint without limiting their aggregate CPU consumption. A role containing the high-privilege change_authentication capability and enabled Splunk Web are required; exploitation drives CPU high until the instance is restarted.
The record
- CVE
- CVE-2025-20370
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-400, T1499.003
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0 <10.0.1
- Affected versionversion=9.2 <9.2.8
- Affected versionversion=9.3 <9.3.6
- Affected versionversion=9.4 <9.4.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo