[ CVE-2026-76277 · Published 7 Oct 2026 ]
Vulnerability in Splunk Enterprise
[ Description ]Official 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.
[ Fixes ]Fixes and patches
No fix or interim patch is linked from our sources yet. Check the vendor references below and limit exposure of affected systems until a fix is available.
[ Advisories ]Government CERT advisories
-
NCSC-NLNCSC-2026-0412
Vulnerabilities fixed in Splunk Enterprise Translated from Dutch
-
CERT-FRCERTFR-2026-AVI-1281
Multiple vulnerabilities in Splunk products Translated from French
Multiple vulnerabilities have been discovered in Splunk products. Some of them allow an attacker to cause remote arbitrary code execution, privilege escalation and a breach of data confidentiality.
-
BSI CERT-BundWID-SEC-2026-3799
Splunk Enterprise: Multiple vulnerabilities Translated from German
[ References ]References
- advisory.splunk.com/advisories/SVD-2026-1001Vendor Advisory