Medium severity · published Aug 19, 2026
CVE-2026-76340
Missing Authorization for Reloading Token-Signing Keys through the REST API in Splunk Enterprise
5.3
CVSS
0.4%
EPSS
No
On KEV
Description
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 change_authentication 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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 31% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SE
Splunk Enterprise · Splunk
10.4 before 10.4.2 · source: vendor
SP
Splunk · Splunk
10.4.0 before 10.4.2 · source: NVD
Affected product
SE
Splunk Enterprise
Splunk
More from Splunk Enterprise
9.8
CVE-2026-20253
Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk Enterprise
9.9
CVE-2026-76302
Security Hardening in Splunk Enterprise - October 2026
9.9
CVE-2026-76299
Security Hardening in Splunk Enterprise - October 2026
9.8
CVE-2026-76301
Security Hardening in Splunk Enterprise - October 2026
9.8
CVE-2026-76285
Improper Adherence to Coding Standards in Splunk Enterprise