CVE-2025-20231 [High] | Information Disclosure in Splunk

In Splunk Enterprise versions below 9.4.1, 9.3.3, 9.2.5, and 9.1.8, and versions below 3.8.38 and 3.7.23 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 run a search using the permissions of a higher-privileged user that could lead to disclosure of sensitive information.<br><br>The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated 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-05-05	0.19%	0.14%	-0.05%
2	2026-05-04	0.05%	0.19%	+0.14%
3	2025-12-20	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-05

0.19%

0.14%

-0.05%

2026-05-04

0.05%

0.19%

+0.14%

2025-12-20

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.1	3.1	HIGH	`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. 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:H) Serious risk that confidential data gets exposed in a big 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.	1.2	5.9	[email protected]
5.7	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N` 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:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.1	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.1

3.1

HIGH

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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:H): Serious risk that confidential data gets exposed in a big 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.

1.2

5.9

[email protected]

5.7

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N 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:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

2.1

3.6

[email protected]

Affected software / configurations for CVE-2025-20231

Vendor	Product	Version	Raw CPE
splunk	splunk	>= 9.1.0, < 9.1.8	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.2.0, < 9.2.5	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.3.0, < 9.3.3	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	9.4.0	cpe:2.3:a:splunk:splunk:9.4.0::::enterprise:::
splunk	splunk_secure_gateway	>= 3.7.0, < 3.7.23	cpe:2.3:a:splunk:splunk_secure_gateway::::::::
splunk	splunk_secure_gateway	>= 3.8.0, < 3.8.38	cpe:2.3:a:splunk:splunk_secure_gateway::::::::

References for CVE-2025-20231

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

URL

CVE-2025-20231 | Sensitive Information Disclosure in Splunk Secure Gateway App

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

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

Weakness enumeration for CVE-2025-20231

Affected software / configurations for CVE-2025-20231

References for CVE-2025-20231