CVE-2026-76534 in Splunk
Summary
by MITRE • 11/20/2026
In Splunk Enterprise for Windows versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the edit_user capability could create multiple user accounts that share the same user directory. This could expose user-specific configuration between those accounts, let one account modify configuration used by another account, or disrupt features that depend on separate user directories. The vulnerability is caused by improper validation of usernames before Splunk Enterprise performs Windows filesystem operations. Windows removes trailing periods from directory names, so distinct usernames can resolve to the same user directory. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified in Splunk Enterprise for Windows versions prior to 10.4.4, 10.2.8, 10.0.11, and 9.4.16 represents a critical flaw in user account management stemming from improper input validation during filesystem operations. This issue specifically affects users who possess the edit_user capability within the Splunk platform's role-based access control model. The core technical failure lies in how the application handles username strings before creating corresponding directories on the Windows operating system. Specifically, the software fails to sanitize or validate usernames for characters that have special significance in the NTFS file system, most notably trailing periods. This oversight allows an attacker with sufficient privileges to manipulate the underlying storage structure of user configurations by exploiting OS-level behavior rather than application logic errors alone.
The operational mechanism of this vulnerability relies on a discrepancy between how Splunk Enterprise processes usernames and how Windows handles directory naming conventions. When a new user account is created, Splunk attempts to create a dedicated directory for that user's configuration files. However, the Microsoft Windows file system automatically strips trailing periods from directory names during creation or access operations. Consequently, if an attacker creates two distinct accounts with usernames that differ only by the presence of one or more trailing dots, both accounts will resolve to the exact same physical directory on disk. For example, a user named admin and another named admin... would both map to the identical folder path within the Splunk data structure. This collision effectively merges the separate identity spaces intended for each account into a single shared storage location.
The security implications of this flaw are severe, primarily centering around unauthorized access modification and configuration tampering. Because multiple user accounts now share the same underlying directory, any changes made to the configuration files by one user will be immediately visible and modifiable by another user sharing that directory. This breaks the fundamental isolation principle required for multi-tenant or role-separated environments within Splunk Enterprise. An attacker could exploit this to overwrite security settings, modify authentication parameters, or inject malicious configurations into a target account's profile without directly possessing the permissions of that target account. Furthermore, features relying on distinct user directories may experience unexpected behavior or disruption, potentially leading to service instability or denial of service conditions for legitimate users whose data becomes corrupted or inaccessible due to conflicting writes from multiple accounts.
From an industry standard perspective, this vulnerability aligns with CWE-20 Improper Input Validation and CWE-78 OS Command Injection principles related to path traversal and resource management failures. It also relates to CWE-694 Use of Multiple Resources with Identical Identifier, where the system fails to ensure unique identifiers for distinct entities, leading to confusion in access control enforcement. In terms of the MITRE ATT&CK framework, this flaw facilitates lateral movement and privilege escalation techniques by allowing an attacker to manipulate configurations associated with higher-privileged accounts through a lower-privileged account that shares its storage path. It represents a classic case where application-level security controls are undermined by operating system quirks not adequately accounted for in the software design.
To mitigate this vulnerability, organizations running affected versions of Splunk Enterprise must upgrade immediately to version 10.4.4 or later, as well as the respective maintenance releases for earlier major branches such as 10.2.8, 10.0.11, and 9.4.16. These updated versions include patches that enforce stricter validation rules on usernames before they are passed to Windows filesystem APIs, ensuring that trailing periods or other problematic characters do not result in directory name collisions. In the interim, administrators should review roles assigned with edit_user capabilities and restrict them to trusted personnel only. Additionally, implementing strict naming conventions for user accounts can help reduce risk until patches are applied. Regular audits of Splunk configuration files and monitoring for unusual changes in user directories can also aid in detecting potential exploitation attempts before significant damage occurs.