CVE-2025-20321 Membership State Change in Splunk Search Head Cluster through a Cross-Site Request Forgery (CSRF) in Splunk Enterprise

Medium 6.5 Published Updated

An unauthenticated attacker can change Search Head Cluster membership state via CSRF, potentially removing the captain or members.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2025-20321?

CVE-2025-20321 is a medium-severity vulnerability in Splunk Splunk, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official 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.114, and 9.2.2406.119, an unauthenticated attacker can send a specially-crafted SPL search that could change the membership state in a Splunk Search Head Cluster (SHC) through a Cross-Site Request Forgery (CSRF), potentially leading to the removal of the captain or a member of the SHC.<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.

Weakness: CWE-352

Which versions are affected by CVE-2025-20321?

It affects 2 products.

Products include Splunk Splunk, Splunk Splunk Cloud Platform.

How do I fix CVE-2025-20321?

No fix has been published for CVE-2025-20321 yet. Limit exposure of the affected software until one is available.

Is CVE-2025-20321 being exploited?

There is no known exploitation of CVE-2025-20321 in the wild and no public exploit code.

All Splunk Splunk vulnerabilities

Sources

Also known as GHSA-v5r8-cj77-2qp9.

Is CVE-2025-20321 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free