cve.bz

CVE-2026-20202 splunk: Improper Handling of Unicode Encoding

6.6 mediumEPSS 0.2%

Medium (6.6) in splunk. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.6 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-04-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-176 Improper Handling of Unicode Encoding
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-20202 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-20202?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-20202?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-20202 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Splunk Enterprisefrom 10.2 before 10.2.2
Splunk Enterprisefrom 10.0 before 10.0.5
Splunk Enterprisefrom 9.4 before 9.4.10
Splunk Enterprisefrom 9.3 before 9.3.11
Splunk Cloud Platformfrom 10.4.2603 before Not Affected
Splunk Cloud Platformfrom 10.3.2512 before 10.3.2512.6
Splunk Cloud Platformfrom 10.2.2510 before 10.2.2510.10
Splunk Cloud Platformfrom 10.1.2507 before 10.1.2507.20
Splunk Cloud Platformfrom 10.0.2503 before 10.0.2503.13
Splunk Cloud Platformfrom 9.3.2411 before 9.3.2411.127

Attack patterns (CAPEC)

  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON