Risky command safeguards bypass using the “/services/streams/search“ REST endpoint through “q“ parameter in Splunk Enterprise
Advisory ID: SVD-2025-1102
CVE ID: CVE-2025-20379
Published: 2025-11-12
Last Update: 2025-11-12
CVSSv3.1 Score: 3.5, Low
CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
CWE: CWE-200
Bug ID: VULN-41203
Description
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.
Solution
Upgrade Splunk Enterprise to versions 10.0.1, 9.4.5, 9.3.7, 9.2.9, or higher.
Splunk is actively monitoring and patching Splunk Cloud Platform instances.
Product Status
| Product | Base Version | Component | Affected Version | Fix Version |
|---|---|---|---|---|
| Splunk Enterprise | 10.0 | Splunk Web | 10.0.0 | 10.0.1 |
| Splunk Enterprise | 9.4 | Splunk Web | 9.4.0 to 9.4.4 | 9.4.5 |
| Splunk Enterprise | 9.3 | Splunk Web | 9.3.0 to 9.3.6 | 9.3.7 |
| Splunk Enterprise | 9.2 | Splunk Web | 9.2.0 to 9.2.8 | 9.2.9 |
| Splunk Cloud Platform | 9.3.2411 | Splunk Web | Below 9.3.2411.116 | 9.3.2411.116 |
| Splunk Cloud Platform | 9.3.2408 | Splunk Web | Below 9.3.2408.124 | 9.3.2408.124 |
| Splunk Cloud Platform | 10.0.2503 | Splunk Web | Below 10.0.2503.5 | 10.0.2503.5 |
| Splunk Cloud Platform | 10.1.2507 | Splunk Web | Below 10.1.2507.1 | 10.1.2507.1 |
Mitigations and Workarounds
The vulnerability affects instances with Splunk Web turned on, turning Splunk Web off is a possible workaround. See Disable unnecessary Splunk Enterprise components and the web.conf configuration specification file for more information on disabling Splunk Web.
Detections
None
Severity
Splunk rates this vulnerability a 3.5, Low, with a CVSSv3.1 vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N.
Acknowledgments
Anton (therceman)