Quick answers
- Is CVE-2026-76340 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76340 being exploited in the wild.
- How severe is CVE-2026-76340?
- Medium severity, with a CVSS score of 5.3, published 19 August 2026.
- Which products and versions are affected?
- Splunk Enterprise 10.4.0 to 10.4.1.
- Is there a fix for CVE-2026-76340?
- A patch was published on 2026-08-19: Fixed in version 10.4.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76340 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-76340?
- Check whether you run Splunk. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a missing authorization vulnerability (CWE-862) in the Splunk Enterprise REST API. The token-key reload action does not validate authentication status or the change_authentication capability, allowing unauthenticated users to trigger the operation. An attacker can make a network request to the affected REST endpoint without credentials to reload the token-signing keys. This could cause denial of service or disrupt authentication-dependent features. The vulnerability is limited to Splunk Enterprise 10.4.0 and 10.4.1; versions below 10.4 are unaffected. Patch available in version 10.4.2 and later.
Affected products
- Splunk Enterprise 10.4.0 to 10.4.1
Timeline
- 2026-08-19: disclosed
- 2026-08-19: patched: Fixed in version 10.4.2