CVE-2025-20322

Denial of Service (DoS) in Search Head Cluster through Cross-Site Request Forgery (CSRF) in Splunk Enterprise

MEDIUM
4.3
CVSS Score
Published: July 7, 2025 at 05:48 PM UTC
Updated: June 17, 2026 at 08:41 AM UTC
2 products affected across 1 vendorSplunkSplunk Cloud Platform

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
Severity
MEDIUM4.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.104, 9.3.2408.113, and 9.2.2406.119, an unauthenticated attacker could send a specially-crafted SPL search command that could trigger a rolling restart in the Search Head Cluster through a Cross-Site Request Forgery (CSRF), potentially leading to a denial of service (DoS).<br><br>The vulnerability requires the attacker to phish the administrator-level victim by tricking them into initiating a request within their browser. The attacker should not be able to exploit the vulnerability at will.<br><br>See [How rolling restart works](https://docs.splunk.com/Documentation/Splunk/9.4.2/DistSearch/RestartSHC) for more information.

Affected

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

9.1 ≤ v < 9.1.109.1.0 ≤ v < 9.1.109.2 ≤ v < 9.2.79.2.0 ≤ v < 9.2.79.2.2406 ≤ v < 9.2.2406.1199.3 ≤ v < 9.3.59.3.0 ≤ v < 9.3.59.3.2408 ≤ v < 9.3.2408.1139.3.2411 ≤ v < 9.3.2411.1049.4 ≤ v < 9.4.39.4.0 ≤ v < 9.4.39.19.29.2.24069.39.3.24089.3.24119.4
Affected range stops below 9.1.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.2406.119, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2408.113, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2411.104, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.3, so it looks safe — our inference, not a vendor statement
9.2.2406 ≤ v < 9.2.2406.1199.3.2408 ≤ v < 9.3.2408.1139.3.2411 ≤ v < 9.3.2411.1049.2.24069.3.24089.3.2411
Affected range stops below 9.2.2406.119, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2408.113, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2411.104, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

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

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

4.3MEDIUMcisco
Vector?

Quick Info

StatusANALYZED
CWE
CWE-352

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.

Free plan, no card