Vulnerability Details CVE-2026-76277
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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.002
EPSS Ranking 7.3%
CVSS Severity
CVSS v3 Score 4.1
Products affected by CVE-2026-76277
-
cpe:2.3:a:splunk:splunk:10.0.0
-
cpe:2.3:a:splunk:splunk:10.0.1
-
cpe:2.3:a:splunk:splunk:10.0.2
-
cpe:2.3:a:splunk:splunk:10.0.3
-
cpe:2.3:a:splunk:splunk:10.0.4
-
cpe:2.3:a:splunk:splunk:10.0.5
-
cpe:2.3:a:splunk:splunk:10.0.7
-
cpe:2.3:a:splunk:splunk:10.0.8
-
cpe:2.3:a:splunk:splunk:10.0.9
-
cpe:2.3:a:splunk:splunk:10.2.0
-
cpe:2.3:a:splunk:splunk:10.2.1
-
cpe:2.3:a:splunk:splunk:10.2.2
-
cpe:2.3:a:splunk:splunk:10.2.4
-
cpe:2.3:a:splunk:splunk:10.2.5
-
cpe:2.3:a:splunk:splunk:10.2.6
-
cpe:2.3:a:splunk:splunk:10.4.0
-
cpe:2.3:a:splunk:splunk:10.4.1
-
cpe:2.3:a:splunk:splunk:10.4.2