CVE-2026-76277Improper Input Validation of Native Splunk Usernames through the REST API in Splunk Enterprise
Description
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.
Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.
Affected products and versions
| Vendor | Product | Versions | |
|---|---|---|---|
| splunk | splunk | 9.4.0 – < 9.4.15 | |
| Splunk | Splunk Enterprise | 10.4 – < 10.4.3, 10.2 – < 10.2.7, 10.0 – < 10.0.10, 9.4 – < 9.4.15 |
References and patches
- https://advisory.splunk.com/advisories/SVD-2026-1001 Vendor Advisory
CPE matches (NVD) (4)
cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*≥ 9.4.0 < 9.4.15cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*≥ 10.0.0 < 10.0.10cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*≥ 10.2.0 < 10.2.7cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*≥ 10.4.0 < 10.4.3