CVE-2025-20226: Risky command safeguards bypass in “/services/streams/search“ endpoint through “q“ parameter in Splunk Enterprise
In Splunk Enterprise versions below 9.4.1, 9.3.3, 9.2.5, and 9.1.8 and Splunk Cloud Platform versions below 9.3.2408.107, 9.2.2406.111, and 9.1.2308.214, 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 on the "/services/streams/search" endpoint through its "q" parameter. 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-20226?
CVE-2025-20226 is classified as a low-severity vulnerability affecting specific versions of Splunk Enterprise and Splunk Cloud Platform.
How do I fix CVE-2025-20226?
To mitigate CVE-2025-20226, upgrade to Splunk Enterprise version 9.4.1 or later, or Splunk Cloud Platform version 9.3.2408.107 or later.
Who is affected by CVE-2025-20226?
CVE-2025-20226 affects low-privileged users who can execute saved searches with risky commands in the specified Splunk versions.
What are the affected versions of Splunk for CVE-2025-20226?
Affected versions for CVE-2025-20226 include Splunk Enterprise versions below 9.4.1, 9.3.3, 9.2.5, and 9.1.8, as well as Splunk Cloud Platform versions below 9.3.2408.107, 9.2.2406.111, and 9.1.2308.214.
What commands can be run by a low-privileged user in CVE-2025-20226?
In CVE-2025-20226, a low-privileged user can run saved searches using risky commands that could potentially impact system security.