CVE-2025-20370 is a denial-of-service vulnerability affecting Splunk Enterprise before 10.0.1, 9.4.4, 9.3.6, and 9.2.8, and Splunk Cloud Platform before 9.3.2411.108, 9.3.2408.118, and 9.2.2406.123. A user assigned a role that includes the high-privilege capability change_authentication can repeatedly send LDAP bind requests to a specific internal endpoint. This can drive sustained high CPU utilization on the Splunk instance and exhaust processing capacity. The condition can persist until the affected Splunk Enterprise instance is restarted, resulting in service degradation or loss of availability.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A denial-of-service vulnerability in Splunk where users with the change_authentication privilege can overload the server with LDAP bind requests.
A medium-severity DoS vulnerability in Splunk Enterprise and Cloud Platform where a user with change_authentication capability can cause high CPU usage and require a restart.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.