CVE-2026-76340: Missing Authorization for Reloading Token-Signing Keys through the REST API in Splunk Enterprise
In Splunk Enterprise 10.4 versions below 10.4.2, an unauthenticated user could cause Splunk Enterprise to reload token-signing keys through the Representational State Transfer (REST) API. The vulnerability does not affect Splunk Enterprise versions below 10.4. The vulnerability is possible because the REST API does not require authentication or the changeauthentication capability for the token-key reload action. 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.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.4.2 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.2.6 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.0.9 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 9.4.14
Event History
Frequently Asked Questions
Which deployments are affected?
Splunk Enterprise 10.4 versions earlier than 10.4.2 are affected. Versions below 10.4 are not affected.
Does an attacker need credentials or any special role capability?
No. The token-key reload REST API action can be triggered by an unauthenticated user because it does not require authentication or the change_authentication capability.
What is the practical impact of exploitation?
An unauthenticated attacker can cause Splunk Enterprise to reload its token-signing keys through the REST API. The provided data identifies integrity impact only and does not describe confidentiality or availability impact.