CVE-2026-76536: Splunk Enterprise · When an actor claims to have a given identity, the software does not prove or insufficiently proves
Affects Splunk EnterpriseSource CVE Database V5
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, 20:06 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 18 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
Apply the official patches by upgrading to Splunk Enterprise versions 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later, where this vulnerability is fixed. No other mitigations are specified. Since this is a critical vulnerability with a high CVSS score, prompt patching is strongly recommended.
Description
CVE-2026-76536 is a critical vulnerability in Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.17. It allows an unauthenticated attacker to read and modify clustering configuration on a standalone instance via the cluster configuration REST API by exploiting acceptance of an empty clustering shared secret. This can expose sensitive configuration data, enable persistence of attacker-controlled settings, and disrupt clustering operations.