CVE-2026-20202 | Improper Input Validation during User Account Creation in Splunk Enterprise

In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions below 10.4.2603.0, 10.3.2512.6, 10.2.2510.10, 10.1.2507.20, 10.0.2503.13, and 9.3.2411.127, a user who holds a role that contains the high-privilege capability `edit_user`could create a specially crafted username that includes a null byte or a non-UTF-8 percent-encoded byte due to improper input validation.<br><br>This could lead to inconsistent conversion of usernames into a proper format for storage and account management inconsistencies, such as being unable to edit or delete affected users.

Published: 2026-04-15 Last update: 2026-04-17 Assigner: [email protected] Source: [email protected]

NVD Status：Analyzed，CVE State: published

View at NVD, CVE.org, EUVD

Conclusion & alert: CVE-2026-20202 is rated Low Risk (32/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.25%). 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-2026-20202

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-06-15	0.05%	0.25%	+0.19%
2	2026-04-21	0.04%	0.05%	+0.02%
3	2026-04-16	—	0.04%	—

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-20202

CVSS metrics for this CVE.

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.6	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/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:H) They need powerful rights—admin, root, or similar—before this pays off. 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: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.	0.7	5.9	[email protected]

Weakness enumeration for CVE-2026-20202

CWE-176 MITRE ↗

Affected software / configurations for CVE-2026-20202

Vendor	Product	Version	Raw CPE
splunk	splunk	>= 9.3.0, < 9.3.11	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 9.4.0, < 9.4.10	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 10.0.0, < 10.0.5	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk	>= 10.2.0, < 10.2.2	cpe:2.3:a:splunk:splunk:::::enterprise:::*
splunk	splunk_cloud_platform	>= 9.3.2411, < 9.3.2411.127	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_cloud_platform	>= 10.0.2503, < 10.0.2503.13	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_cloud_platform	>= 10.1.2507, < 10.1.2507.20	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_cloud_platform	>= 10.2.2510, < 10.2.2510.10	cpe:2.3:a:splunk:splunk_cloud_platform::::::::
splunk	splunk_cloud_platform	>= 10.3.2512, < 10.3.2512.6	cpe:2.3:a:splunk:splunk_cloud_platform::::::::

References for CVE-2026-20202

URL	Tags
https://advisory.splunk.com/advisories/SVD-2026-0401	Vendor Advisory

cvelogic Threat Intelligence