Vulnerability Details CVE-2025-20379
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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.0
EPSS Ranking 5.2%
CVSS Severity
CVSS v3 Score 3.5
Products affected by CVE-2025-20379
-
cpe:2.3:a:splunk:splunk:10.0.0
-
cpe:2.3:a:splunk:splunk:9.2.0
-
cpe:2.3:a:splunk:splunk:9.2.1
-
cpe:2.3:a:splunk:splunk:9.2.2
-
cpe:2.3:a:splunk:splunk:9.2.3
-
cpe:2.3:a:splunk:splunk:9.2.4
-
cpe:2.3:a:splunk:splunk:9.2.5
-
cpe:2.3:a:splunk:splunk:9.2.6
-
cpe:2.3:a:splunk:splunk:9.2.7
-
cpe:2.3:a:splunk:splunk:9.2.8
-
cpe:2.3:a:splunk:splunk:9.3.0
-
cpe:2.3:a:splunk:splunk:9.3.1
-
cpe:2.3:a:splunk:splunk:9.3.2
-
cpe:2.3:a:splunk:splunk:9.3.3
-
cpe:2.3:a:splunk:splunk:9.3.4
-
cpe:2.3:a:splunk:splunk:9.3.5
-
cpe:2.3:a:splunk:splunk:9.3.6
-
cpe:2.3:a:splunk:splunk:9.4.0
-
cpe:2.3:a:splunk:splunk:9.4.1
-
cpe:2.3:a:splunk:splunk:9.4.2
-
cpe:2.3:a:splunk:splunk:9.4.3
-
cpe:2.3:a:splunk:splunk:9.4.4
-
cpe:2.3:a:splunk:splunk_cloud_platform:10.0.2503
-
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.100
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.101
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.103
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.104
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.107
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.111
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.112
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.113
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.114
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.117
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.118
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.119
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2408.121
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.102
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.103
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.104
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.107
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.108
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.109
-
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.111