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.
Improper Input Validation of Native Splunk Usernames through the REST API in Splunk Enterprise
Problem type
Affected products
Splunk
< 10.4.3 - AFFECTED
< 10.2.7 - AFFECTED
< 10.0.10 - AFFECTED
< 9.4.15 - AFFECTED
References
GitHub Security Advisories
GHSA-f49j-g49x-qqr9
In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, a user that holds a role...
https://github.com/advisories/GHSA-f49j-g49x-qqr9In 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.
JSON source
https://cveawg.mitre.org/api/cve/CVE-2026-76277Click to expand
{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2026-76277",
"assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"assignerShortName": "cisco",
"dateUpdated": "2026-10-08T15:06:09.743Z",
"dateReserved": "2026-08-19T12:02:03.621Z",
"datePublished": "2026-10-07T20:46:35.907Z",
"state": "PUBLISHED"
},
"containers": {
"cna": {
"providerMetadata": {
"orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"shortName": "cisco",
"dateUpdated": "2026-10-07T20:46:35.907Z"
},
"datePublic": "2026-10-07T00:00:00.000Z",
"title": "Improper Input Validation of Native Splunk Usernames through the REST API in Splunk Enterprise",
"descriptions": [
{
"lang": "en",
"value": "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.",
"supportingMedia": [
{
"type": "text/markdown",
"base64": false,
"value": "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": [
{
"vendor": "Splunk",
"product": "Splunk Enterprise",
"modules": [
"REST API"
],
"versions": [
{
"version": "10.4",
"status": "affected",
"versionType": "custom",
"lessThan": "10.4.3"
},
{
"version": "10.2",
"status": "affected",
"versionType": "custom",
"lessThan": "10.2.7"
},
{
"version": "10.0",
"status": "affected",
"versionType": "custom",
"lessThan": "10.0.10"
},
{
"version": "9.4",
"status": "affected",
"versionType": "custom",
"lessThan": "9.4.15"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"lang": "en",
"description": "The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program.",
"cweId": "CWE-20",
"type": "cwe"
}
]
}
],
"references": [
{
"url": "https://advisory.splunk.com/advisories/SVD-2026-1001"
}
],
"metrics": [
{
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
],
"cvssV3_1": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L",
"baseScore": 4.1,
"baseSeverity": "MEDIUM"
}
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher."
}
],
"credits": [
{
"lang": "en",
"value": "Gabriel Nitu, Splunk",
"type": "finder"
}
]
},
"adp": [
{
"providerMetadata": {
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP",
"dateUpdated": "2026-10-08T15:06:09.743Z"
},
"title": "CISA ADP Vulnrichment",
"metrics": [
{}
]
}
]
}
}