CVE-2026-76277

published 7 Oct 2026 · updated 8 Oct 2026

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

4.1MediumCVSS 4.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Enterprise 10.0.10, Enterprise 10.2.7, Enterprise 10.4.3 and 1 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
SplunkEnterprise>=10.0 <10.0.10, >=10.2 <10.2.7, >=10.4 <10.4.3, >=9.4 <9.4.1510.0.10, 10.2.7, 10.4.3, 9.4.15

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Enterprise, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-76277 severity on Zeptric[![CVE-2026-76277](https://zeptric.io/badge/cve/CVE-2026-76277.svg)](https://zeptric.io/cve/CVE-2026-76277)