CVE-2026-76277

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

Published Oct 7, 2026 CVSS 3.1 · 4.1 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

This vulnerability arises when a Splunk Enterprise user with the edit_user capability creates a native username ending with a period because the system fails to reject the trailing character before locating the user directory. The flaw allows distinct usernames to share per‑user configuration data, leading to unintended modifications of configuration files or user‑management actions that affect the wrong account. The result is loss of configuration integrity and potential privilege escalation if an attacker can influence another account’s settings. This issue is captured as CWE‑20, improper input validation.

Affected Systems

Splunk Enterprise deployments running any version prior to 10.4.3, 10.2.7, 10.0.10, or 9.4.15 that grant edit_user privileges through the REST API are susceptible. All roles possessing edit_user capability, including trusted administrators, are impacted.

Risk and Exploitability

The CVSS score of 4.1 indicates a moderate severity. An EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is an authenticated REST API session with edit_user rights; no evidence indicates a network‑based exploitation path without such credentials. Damage is primarily limited to configuration integrity, but the ability to target another account’s configuration could facilitate privilege escalation, though the impact remains constrained compared to remote code execution.

Remediation

Vendor Solution

Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher.


OpenCVE Recommended Actions

  • Upgrade Splunk Enterprise to at least 10.4.3 (or 10.2.7, 10.0.10, or 9.4.15) as provided by the vendor
  • Restrict the edit_user capability to only trusted administrators and review role assignments for unnecessary permissions
  • Implement additional input validation or audit logging to detect and block usernames that end with a period if an immediate upgrade is not possible

Generated by OpenCVE AI on October 7, 2026 at 23:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Splunk splunk
CPEs cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
Vendors & Products Splunk splunk
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Splunk
Splunk splunk Enterprise
Vendors & Products Splunk
Splunk splunk Enterprise
Type Values Removed Values Added
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.
Title Improper Input Validation of Native Splunk Usernames through the REST API in Splunk Enterprise
Weaknesses CWE-20
References
Metrics cvssV3_1

{'score': 4.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L'}

Weaknesses
  • CWE-20

    Improper Input Validation

Sources

Status
PUBLISHED
Assigner
cisco
Published
Updated
Oct 8, 2026, 3:06 PM
Reserved
Aug 19, 2026, 12:02 PM
Status
Analyzed
Published
Oct 7, 2026, 9:17 PM
Modified
Oct 14, 2026, 12:03 PM