Improper Input Validation of Native Splunk Usernames through the REST API in Splunk Enterprise

Summary

In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, a user that holds a role with the edit_user capability could create a native Splunk username that ends with a period. The vulnerability is possible because username validation does not reject a trailing period before the username is used for a user directory. This can cause distinct native Splunk usernames to share per-user configuration data, and user-management operations can affect the wrong account or fail. For more information see Set up native Splunk authentication (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/use-the-native-splunk-platform-authentication-scheme/set-up-native-splunk-authentication) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.

Timeline

1. Oct 7, 2026, 8:46 PM UTCCVE published
2. Oct 8, 2026, 3:05 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Oct 8, 2026, 3:06 PM UTCRecord last updated

Affected versions

• Splunk Splunk Enterprise

  From 10.4 · fixed in 10.4.3; From 10.2 · fixed in 10.2.7; From 10.0 · fixed in 10.0.10; From 9.4 · fixed in 9.4.15

References 1