CVE-2026-20202: In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions below…
CVE-2026-20202 · Severity: medium · CVSS 6.6 · Published 2026-04-15
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.
No. Junglewise Threat Intelligence has no report of CVE-2026-20202 being exploited in the wild.
How severe is CVE-2026-20202?
Medium severity, with a CVSS score of 6.6, published 15 April 2026.
Which products and versions are affected?
Splunk, Splunk Cloud Platform. The advisory does not name versions.
Is there a fix for CVE-2026-20202?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-20202?
Check whether you run Splunk or Splunk Cloud Platform. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.