CVE-2026-76277
published 2026-10-07CVE-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…
PriorityP422medium4.1CVSS 3.1
AVNACHPRHUINSUCLILAL
EPSS
0.18%
7.5th percentile
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.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| splunk | splunk | >= 10.0.0 < 10.0.10 | 10.0.10 |
| splunk | splunk | >= 10.2.0 < 10.2.7 | 10.2.7 |
| splunk | splunk | >= 10.4.0 < 10.4.3 | 10.4.3 |
| splunk | splunk | >= 9.4.0 < 9.4.15 | 9.4.15 |
| splunk | splunk_enterprise | >= 10.0 < 10.0.10 | 10.0.10 |
| splunk | splunk_enterprise | >= 10.2 < 10.2.7 | 10.2.7 |
| splunk | splunk_enterprise | >= 10.4 < 10.4.3 | 10.4.3 |
| splunk | splunk_enterprise | >= 9.4 < 9.4.15 | 9.4.15 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
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.
ghsa_unreviewed·2026-10-07
CVE-2026-76277 [MEDIUM] CWE-20 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.
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.s
VulDB
Splunk Enterprise up to 9.4.14/10.0.9/10.2.6/10.4.2 Username Validation privileges management
vuldb·2026-10-07·CVSS 4.1
CVE-2026-76277 [MEDIUM] Splunk Enterprise up to 9.4.14/10.0.9/10.2.6/10.4.2 Username Validation privileges management
A vulnerability classified as problematic has been found in Splunk Enterprise up to 9.4.14/10.0.9/10.2.6/10.4.2. This issue affects some unknown processing of the component Username Validation. Performing a manipulation results in improper privilege management.
This vulnerability is known as CVE-2026-76277. Remote exploitation of the attack is possible. No exploit is available.
It is recommended to upgrade the affected component.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-10-07
Published