CVE-2026-20202

Improper Input Validation during User Account Creation in Splunk Enterprise

MEDIUM
6.6
CVSS Score
Published: April 15, 2026 at 03:17 PM UTC
Updated: June 17, 2026 at 10:17 AM UTC
2 products affected across 1 vendorSplunkSplunk Cloud Platform

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.6
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.0 ≤ v < 10.0.510.0.0 ≤ v < 10.0.510.2 ≤ v < 10.2.210.2.0 ≤ v < 10.2.29.3 ≤ v < 9.3.119.3.0 ≤ v < 9.3.119.4 ≤ v < 9.4.109.4.0 ≤ v < 9.4.1010.010.29.39.4
Affected range stops below 10.0.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.10, so it looks safe — our inference, not a vendor statement
10.0.2503 ≤ v < 10.0.2503.1310.1.2507 ≤ v < 10.1.2507.2010.2.2510 ≤ v < 10.2.2510.1010.3.2512 ≤ v < 10.3.2512.610.4.2603 ≤ v < Not Affected9.3.2411 ≤ v < 9.3.2411.12710.0.250310.1.250710.2.251010.3.251210.4.26039.3.2411
Affected range stops below 10.0.2503.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.2507.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.2510.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.3.2512.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2411.127, so it looks safe — our inference, not a vendor statement
Affected range stops below Not Affected, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.6MEDIUMcisco
Vector?

Quick Info

StatusANALYZED
CWE
CWE-176

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card