Improper Input Validation during User Account Creation in Splunk Enterprise
Summary
| CVE | CVE-2026-20202 |
|---|---|
| State | PUBLISHED |
| Assigner | cisco |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-04-15 16:16:34 UTC |
| Updated | 2026-04-17 19:10:36 UTC |
| Description | 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. |
Risk And Classification
Primary CVSS: v3.1 6.6 MEDIUM from [email protected]
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.000410000 probability, percentile 0.123820000 (date 2026-04-20)
Problem Types: CWE-176 | CWE-176 The software does not properly handle when an input contains Unicode encoding.
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Primary | 6.6 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | CVSS | 6.6 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
HighPrivileges Required
HighUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD Known Affected Configurations (CPE 2.3)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Splunk | Splunk Enterprise | affected 10.2 10.2.2 custom | Not specified |
| CNA | Splunk | Splunk Enterprise | affected 10.0 10.0.5 custom | Not specified |
| CNA | Splunk | Splunk Enterprise | affected 9.4 9.4.10 custom | Not specified |
| CNA | Splunk | Splunk Enterprise | affected 9.3 9.3.11 custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 10.4.2603 Not Affected custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 10.3.2512 10.3.2512.6 custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 10.2.2510 10.2.2510.10 custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 10.1.2507 10.1.2507.20 custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 10.0.2503 10.0.2503.13 custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 9.3.2411 9.3.2411.127 custom | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| advisory.splunk.com/advisories/SVD-2026-0401 | [email protected] | advisory.splunk.com | Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Ryan Luke<br><br>Mahfujur Rahman (mahfujwhh) (en)
There are currently no legacy QID mappings associated with this CVE.