CVE-2025-20379

Dec. 3, 2025, 9:41 p.m.

3.5
Low

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.

Product(s) Impacted

Vendor Product Versions
Splunk
  • Splunk
  • Splunk Cloud Platform
  • *, 10.0.0
  • *

Weaknesses

Common security weaknesses mapped to this vulnerability.

CWE-200
Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

*CPE(s)

Affected systems and software identified for this CVE.

Type Vendor Product Version Update Edition Language Software Edition Target Software Target Hardware Other Information
a splunk splunk / / / / enterprise / / /
a splunk splunk / / / / enterprise / / /
a splunk splunk / / / / enterprise / / /
a splunk splunk 10.0.0 / / / enterprise / / /
a splunk splunk_cloud_platform / / / / / / / /
a splunk splunk_cloud_platform / / / / / / / /
a splunk splunk_cloud_platform / / / / / / / /
a splunk splunk_cloud_platform / / / / / / / /

CVSS Score

3.5 / 10

CVSS Data - 3.1

  • Attack Vector: NETWORK
  • Attack Complexity: LOW
  • Privileges Required: LOW
  • Scope: UNCHANGED
  • Confidentiality Impact: LOW
  • Integrity Impact: NONE
  • Availability Impact: NONE
  • CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

    View Vector String

Timeline

Published: Nov. 12, 2025, 6:15 p.m.
Last Modified: Dec. 3, 2025, 9:41 p.m.

Status : Analyzed

CVE has had analysis completed and all data associations made.

More info

Source

psirt@cisco.com

*Disclaimer: Some vulnerabilities do not have an associated CPE. To enhance the data, we use AI to infer CPEs based on CVE details. This is an automated process and might not always be accurate.