Skip to main content
VulnerabilityPublished

CVE-2026-20202: Splunk Enterprise · The software does not properly handle when an input contains Unicode encoding.

Affects Splunk EnterpriseSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.6 Medium · fixed in 10.2.2 : update Splunk Enterprise when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
6.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.2.2, 10.0.5, 9.4.10 +6
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.2 <10.2.2
Fixed in
  • 10.2.2
SplunkSplunk EnterpriseAffected
  • >=10.0 <10.0.5
Fixed in
  • 10.0.5
SplunkSplunk EnterpriseAffected
  • >=9.4 <9.4.10
Fixed in
  • 9.4.10
SplunkSplunk EnterpriseAffected
  • >=9.3 <9.3.11
Fixed in
  • 9.3.11
SplunkSplunk Cloud PlatformAffected
  • >=10.3.2512 <10.3.2512.6
  • >=10.2.2510 <10.2.2510.10
  • >=10.1.2507 <10.1.2507.20
  • >=10.0.2503 <10.0.2503.13
  • >=9.3.2411 <9.3.2411.127
  • =10.4.2603
Fixed in
  • 10.3.2512.6
  • 10.2.2510.10
  • 10.1.2507.20
  • 10.0.2503.13
  • 9.3.2411.127

AI-suggested

If you cannot patch yet, administrators should carefully control and audit users with the 'edit_user' capability to prevent creation of usernames containing null bytes or non-UTF-8 percent-encoded bytes. Avoid creating or accepting usernames with unusual encoding to mitigate the risk of account management inconsistencies.

Description

CVE-2026-20202 is a vulnerability in Splunk Enterprise and certain Splunk Cloud Platform versions where improper handling of usernames containing null bytes or non-UTF-8 percent-encoded bytes can cause account management inconsistencies. This affects versions prior to 10.2.2, 10.0.5, 9.4.10, and 9.3.11 for Splunk Enterprise, and specified earlier versions for Splunk Cloud Platform.

References

Community reviews

Loading reviews…