Cyber Resilience

CVE-2025-20320

Splunk 9.1.0 – 9.1.10

Published
07 July 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 6.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H
EPSS Score 0.0037 30th percentile
Risk Priority 48 floored blend · peak EPSS

Summary

CVE-2025-20320 is a medium-severity Path Traversal: '.../...//' (CWE-35) vulnerability in Splunk Splunk. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In Splunk Enterprise versions below 9.4.3, 9.3.5, 9.2.7 and 9.1.10, and Splunk Cloud Platform versions below 9.3.2411.107, 9.3.2408.117, and 9.2.2406.121, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a malicious payload through the…

more

`User Interface - Views` configuration page that could potentially lead to a denial of service (DoS).The user could cause the DoS by exploiting a path traversal vulnerability that allows for deletion of arbitrary files within a Splunk directory. The vulnerability requires the low-privileged user to phish the administrator-level victim by tricking them into initiating a request within their browser. The low-privileged user should not be able to exploit the vulnerability at will.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-32706Same product: Splunk Splunk
CVE-2025-20322Same product: Splunk Splunk
CVE-2025-20228Same product: Splunk Splunk
CVE-2025-20388Same product: Splunk Splunk
CVE-2026-20252Same product: Splunk Splunk
CVE-2025-20371Same product: Splunk Splunk
CVE-2026-20297Same product: Splunk Splunk
CVE-2025-20321Same product: Splunk Splunk
CVE-2026-20296Same product: Splunk Splunk
CVE-2024-45737Same product: Splunk Splunk

Affected Assets

splunk
splunk
9.1.0 — 9.1.10 · 9.2.0 — 9.2.7 · 9.3.0 — 9.3.5
splunk
splunk cloud platform
9.2.2406 — 9.2.2406.121 · 9.3.2408 — 9.3.2408.117 · 9.3.2411 — 9.3.2411.107

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly neutralizes path sequences so the traversal cannot be introduced or exploited.

Enforces access authorizations on the resulting pathname, blocking traversal attempts from succeeding.

Enforces information flow rules that stop unauthorized directory escapes via crafted paths.

Least privilege reduces the impact of any successful traversal by limiting accessible resources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that neutralize traversal sequences.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect path-traversal flaws before release.

prevents

Secure SDLC mandates input validation and path-handling controls that directly mitigate path traversal.

prevents

Application security requirements include rules for safe file-path construction and canonicalization.

prevents

Secure architecture principles require proper directory restrictions and input sanitization to prevent traversal.

prevents

Secure coding standards explicitly forbid unsafe path concatenation and mandate canonicalization routines.

mitigates

Information access restriction limits file reachability but does not address the input-validation flaw itself.

References