CVE-2026-76543: Splunk Enterprise · The application generates a query intended to access or manipulate data
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium · fixed in 10.6.1 : update Splunk Enterprise when convenient.
Data as of 19 Nov 2026, 20:07 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.4 |
|---|
- Patch
- Available – fixed in 10.6.1, 10.4.5, 10.2.9 +2
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:NExploitation 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 to a fixed release listed under Affected software.
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
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
Apply the official fixes by upgrading to Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later. Since this is an on-premises product, administrators should prioritize patching affected instances. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-76543 affects Splunk Enterprise versions prior to 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17. It allows a user with the "power" Splunk role to store attacker-controlled Search Processing Language (SPL) in a shared data model due to improper neutralization of data model field names in the Data Model Editor. Exploitation requires phishing to trick the user into initiating a request in their browser. The vulnerability has a medium severity with a CVSS score of 5.4 and has been fixed in the stated versions.