Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

Blind SSRF in Splunk Enterprise and Splunk Cloud Platform

IdentifiersCVE-2025-20371CWE-918· Server-Side Request Forgery (SSRF)

CVE-2025-20371 is a blind server-side request forgery vulnerability in Splunk Enterprise and Splunk Cloud Platform. In affected versions, Splunk processes certain REST API calls in a way that does not adequately validate or restrict user-controlled URLs or related parameters, allowing an unauthenticated attacker to cause the Splunk server to issue arbitrary HTTP requests to attacker-chosen destinations. The issue is described as blind SSRF because the attacker does not directly receive the response body, but can still induce server-side interactions with internal or external services. Under the documented exploitation conditions, the forged requests may be performed in the context of an authenticated high-privileged user, potentially enabling REST API actions through Splunk on that user’s behalf.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an unauthenticated attacker to coerce the Splunk server into making arbitrary outbound requests, including to internal services or Splunk REST API endpoints that are not directly reachable by the attacker. Because the requests may execute in the context of an authenticated high-privileged user, the vulnerability can potentially enable privileged REST API actions, access to sensitive internal resources, and disruption of security monitoring or administrative operations within affected Splunk deployments. Although the SSRF is blind, it still provides a meaningful primitive for interacting with internal services and abusing trust relationships from the Splunk server.

Mitigation

If you can’t patch tonight, do this now.

Where immediate patching is not possible, Splunk recommended disabling Splunk Web if it is not required, restricting assignment and use of high-privilege roles, and setting enableSplunkWebClientNetloc to false in web.conf. Because exploitation is associated with victim-initiated requests, reducing exposure of Splunk Web to untrusted users and minimizing opportunities for phishing or browser-driven interaction can further reduce risk until patches are applied.

Remediation

Patch, then assume compromise.

Upgrade Splunk Enterprise to a fixed release: 10.0.1 or later, 9.4.4 or later, 9.3.6 or later, or 9.2.8 or later, as applicable to the deployed branch. For Splunk Cloud Platform, Splunk indicated that patches are applied automatically and that affected customers will be notified when patching is complete. Validate that deployed instances are at or above the fixed versions referenced for Splunk Cloud Platform: 9.3.2411.109, 9.3.2408.119, and 9.2.2406.122 or later, as applicable.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SplunkSplunkapplication
SplunkSplunk Cloud Platformapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.