CVE-2025-20383 | Improper access control through push notifications for reports and alerts in Splunk Secure Gateway app

In Splunk Enterprise versions below 10.0.2, 9.4.6, 9.3.8, and 9.2.10, and below 3.9.10, 3.8.58, and 3.7.28 of Splunk Secure Gateway app in Splunk Cloud Platform, a low-privileged user that does not hold the "admin" or "power" Splunk roles and subscribes to mobile push notifications could receive notifications that disclose the title and description of the report or alert even if they do not have access to view the report or alert.

Published: 2025-12-03 Last update: 2025-12-05 Assigner: [email protected] Source: [email protected]

NVD Status：Analyzed，CVE State: published

View at NVD, CVE.org, EUVD

Conclusion & alert: CVE-2025-20383 is rated Low Risk (20.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.03%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

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

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-01	0.05%	0.03%	-0.02%
2	2026-04-04	0.03%	0.05%	+0.02%
3	2025-12-04	—	0.03%	—

Full EPSS history (3 records total)

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

CVSS metrics for this CVE.

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:L/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: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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.8	1.4	[email protected]

Weakness enumeration for CVE-2025-20383

CWE-200 MITRE ↗

Affected software / configurations for CVE-2025-20383

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-20383

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

cvelogic Threat Intelligence