CVE-2025-20389 [Medium] | Input Validation Bypass in Splunk

In Splunk Enterprise versions below 10.0.2, 9.4.6, 9.3.8, and 9.2.10, and versions below 3.9.10, 3.8.58 and 3.7.28 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a malicious payload through the `label` column field after adding a new device in the Splunk Secure Gateway app. This could potentially lead to a client-side denial of service (DoS).

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-01	0.16%	0.10%	-0.06%
2	2026-04-04	0.05%	0.16%	+0.11%
3	2025-12-09	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-01

0.16%

0.10%

-0.06%

2026-04-04

0.05%

0.16%

+0.11%

2025-12-09

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L` 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:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. 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:N) Data isn’t meaningfully altered or forged. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	2.8	1.4	[email protected]
6.5	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. 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:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L 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:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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:N): Data isn’t meaningfully altered or forged.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

2.8

1.4

[email protected]

6.5

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

3.6

[email protected]

Affected software / configurations for CVE-2025-20389

Vendor	Product	Version	Raw CPE
splunk	splunk	>= 9.2.0, < 9.2.10	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.3.0, < 9.3.8	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.4.0, < 9.4.6	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 10.0.0, < 10.0.2	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk_cloud_platform	>= 9.3.2411, < 9.3.2411.120	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_cloud_platform	>= 10.0.2503, < 10.0.2503.8	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_cloud_platform	>= 10.1.2507, < 10.1.2507.6	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_secure_gateway	>= 3.7.0, < 3.7.28	cpe:2.3:a:splunk:splunk_secure_gateway::::::::
splunk	splunk_secure_gateway	>= 3.8.0, < 3.8.58	cpe:2.3:a:splunk:splunk_secure_gateway::::::::
splunk	splunk_secure_gateway	>= 3.9.0, < 3.9.10	cpe:2.3:a:splunk:splunk_secure_gateway::::::::

References for CVE-2025-20389

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

URL

CVE-2025-20389 | Improper Input Validation in "label" column field in Splunk Secure Gateway App

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

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

Weakness enumeration for CVE-2025-20389

Affected software / configurations for CVE-2025-20389

References for CVE-2025-20389