CVE-2026-76340: Splunk Enterprise · The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 10.4.2 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
A fixed version, 10.4.2, is available that addresses this vulnerability. Users should upgrade to Splunk Enterprise version 10.4.2 or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-76340 is a medium severity vulnerability in Splunk Enterprise versions 10.4 up to but not including 10.4.2. It allows an unauthenticated user to reload token-signing keys via the REST API because the API does not require authentication or the necessary capability for this action. Versions prior to 10.4 are not affected.