In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could use an empty
Source GCVE Database
Not known to be exploited · CVSS 9.4 Critical · fixed in 10.4.5 : patch Splunk Enterprise as a priority.
Data as of 19 Nov 2026, 22:18 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 9.4 |
|---|
- Patch
- Available – fixed in 10.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 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 19 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.5, 10.2.9, 10.0.12 or 9.4.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
A fix is available in Splunk Enterprise versions 10.4.5, 10.2.9, 10.0.12, and 9.4.17. Users should upgrade to these versions or later to remediate this vulnerability. No other mitigation guidance is provided, and patching is the recommended action.
Description
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where an unauthenticated user can exploit an empty clustering shared secret to access and modify clustering configuration via the REST API on standalone instances. This flaw arises because the software accepts an empty shared secret as valid when clustering is disabled, potentially exposing sensitive configuration and disrupting cluster operations.