CVE-2026-76540: Splunk Enterprise · The software does not perform an authorization check when an actor attempts to access a resource or
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in 10.4.5 : patch Splunk Enterprise soon.
Data as of 19 Nov 2026, 20:06 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 8.8 |
|---|
- Patch
- Available – fixed in 10.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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
Upgrade Splunk Enterprise to version 9.4.17, 10.0.12, 10.2.9, or 10.4.5 or later, where this vulnerability has been fixed. Applying these official patches fully mitigates the issue.
Description
CVE-2026-76540 is a vulnerability in Splunk Enterprise prior to versions 9.4.17, 10.0.12, 10.2.9, and 10.4.5. It allows users without admin or power roles to configure metric alerts via the REST API that execute searches with elevated privileges. This occurs because the software fails to enforce role-based authorization on metric alert configurations, enabling unauthorized data access, modification, and potential disruption of the Splunk instance.