Splunk Enterprise/Cloud Platform Username edit_user unicode encoding
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 4.84 |
Summary
A vulnerability was found in Splunk Enterprise and Cloud Platform and classified as critical. Affected by this issue is the function edit_user of the component Username Handler. The manipulation results in improper handling of unicode encoding.
This vulnerability is reported as CVE-2026-20202. The attack can be launched remotely. No exploit exists.
It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Splunk Enterprise and Cloud Platform (the affected version is unknown). Affected is the function edit_user of the component Username Handler. The manipulation with an unknown input leads to a improper handling of unicode encoding vulnerability. CWE is classifying the issue as CWE-176. The product does not properly handle when an input contains Unicode encoding. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.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.
The advisory is shared for download at advisory.splunk.com. This vulnerability is traded as CVE-2026-20202 since 10/08/2025. The exploitability is told to be difficult. It is possible to launch the attack remotely. Additional levels of successful authentication are required for exploitation. There are known technical details, but no exploit is available.
Upgrading eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.6
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.6
CNA Vector (cisco): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper handling of unicode encodingCWE: CWE-176 / CWE-172
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
10/08/2025 CVE reserved04/15/2026 Advisory disclosed
04/15/2026 VulDB entry created
04/15/2026 VulDB entry last update
Sources
Advisory: SVD-2026-0401Status: Confirmed
CVE: CVE-2026-20202 (🔒)
GCVE (CVE): GCVE-0-2026-20202
GCVE (VulDB): GCVE-100-357732
Entry
Created: 04/15/2026 18:16Changes: 04/15/2026 18:16 (64)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.