CVE-2025-20320 [Medium] | Denial of Service in Splunk

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

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.29%	0.37%	+0.08%
2	2026-05-03	0.05%	0.29%	+0.24%
3	2025-08-27	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.29%

0.37%

+0.08%

2026-05-03

0.05%

0.29%

+0.24%

2025-08-27

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.1	4.2	[email protected]
7.3	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.1	5.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.1

4.2

[email protected]

7.3

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.1

5.2

[email protected]

Affected software / configurations for CVE-2025-20320

Vendor	Product	Version	Raw CPE
splunk	splunk	>= 9.1.0, < 9.1.10	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.2.0, < 9.2.7	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.3.0, < 9.3.5	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.4.0, < 9.4.3	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk_cloud_platform	>= 9.2.2406, < 9.2.2406.121	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_cloud_platform	>= 9.3.2408, < 9.3.2408.117	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_cloud_platform	>= 9.3.2411, < 9.3.2411.107	cpe:2.3:a:splunk:splunk_cloud_platform::::::::

References for CVE-2025-20320

URL	Tags
https://advisory.splunk.com/advisories/SVD-2025-0703	Vendor Advisory

URL

CVE-2025-20320 | Denial of Service (DoS) through “User Interface - Views“ configuration page in Splunk Enterprise

Exploit prediction scoring system (EPSS) score for CVE-2025-20320

Common vulnerability scoring system (CVSS) metrics for CVE-2025-20320

Weakness enumeration for CVE-2025-20320

Affected software / configurations for CVE-2025-20320

References for CVE-2025-20320