Splunk Enterprise and Cloud Platform

CVE-2025-20379: Risky command safeguards bypass using the “/services/streams/search“ REST endpoint through “q“ parameter in Splunk Enterprise

In Splunk Enterprise versions below 10.0.1, 9.4.5, 9.3.7, and 9.2.9 and Splunk Cloud Platform versions below 9.3.2411.116, 9.3.2408.124, 10.0.2503.5 and 10.1.2507.1, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands.

Published

ExploitedNot in CISA KEV
Ransomware useNot reportedPer CISA
SeverityLOWCVSS 3.1 3.5
EPSS0.30%Chance of exploitation in 30 days
Public exploitNot tracked
FixAvailable

Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.

Affected and fixed versions

Product / branchFixed in
Splunk Enterprise 10.010.0.1 or later
Splunk Enterprise 9.49.4.5 or later
Splunk Enterprise 9.39.3.7 or later
Splunk Enterprise 9.29.2.9 or later
Splunk Cloud Platform 9.39.3.2411.116 or later
Splunk Cloud Platform 9.39.3.2408.124 or later
Splunk Cloud Platform 10.010.0.2503.5 or later
Splunk Cloud Platform 10.110.1.2507.1 or later

Always confirm against the vendor advisory, which lists every fixed hotfix.

What it is

In Splunk Enterprise versions below 10.0.1, 9.4.5, 9.3.7, and 9.2.9 and Splunk Cloud Platform versions below 9.3.2411.116, 9.3.2408.124, 10.0.2503.5 and 10.1.2507.1, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands. They could bypass these safeguards on the “/services/streams/search“ endpoint through its “q“ parameter by circumventing endpoint restrictions using character encoding in the REST path. The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will.

Sources

KEV status, EPSS score and vendor data refreshed automatically, last on 13 Oct 2026.

Get alerts

A notification when we publish a new analysis or a covered vendor gets a new actively exploited CVE. No account, no email.