CVE-2026-20202 json
Improper Input Validation during User Account Creation in Splunk Enterprise
published 2026-04-15 6 mo ago modified 2026-10-26 13 d ago also EUVD-2026-22930
- cvss
- 6.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Splunk Splunk Enterprise 9.3.11, 9.4.10, 10.0.5, 10.2.2
- Splunk Splunk Cloud Platform 9.3.2411.127, 10.0.2503.13, 10.1.2507.20, 10.2.2510.10, 10.3.2512.6
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 6 mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.6 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Splunk Splunk Enterprise
- Splunk Splunk Cloud Platform
Classification
- Weakness
-
- CWE-176 Improper Handling of Unicode Encoding
References
-
advisory.splunk.com
/advisories/SVD-2026-0401
vendor-advisory
Sources
- CVE List CVE-2026-20202
- NVD CVE-2026-20202
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.