CVE-2026-76340: In Splunk Enterprise 10.4 versions below 10.4.2, an unauthenticated user could cause Splunk Enterprise to reload token-signing keys through the
Source GCVE Database
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
Splunk has fixed this vulnerability in version 10.4.2. Users should upgrade to Splunk Enterprise 10.4.2 or later to remediate this issue. No other mitigations are indicated.
Description
Splunk Enterprise versions 10.4 prior to 10.4.2 contain a vulnerability where an unauthenticated user can trigger a reload of token-signing keys via the REST API. This occurs because the API does not require authentication or the necessary capability for this action. The issue does not affect versions below 10.4. The vulnerability has a moderate severity score of 5.3 CVSS and does not impact confidentiality or availability but allows integrity impact through unauthorized key reloads.