CVE-2026-76541: Splunk Enterprise · The software constructs all or part of a command using externally-influenced input from an upstream
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium · fixed in 10.4.5 : 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 | 4.8 |
|---|
- Patch
- Available – fixed in 10.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/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 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 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated in the advisory.
Description
CVE-2026-76541 affects Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.17. A user with the "power" role can inject attacker-controlled Search Processing Language (SPL) into shared data model calculations. When another user runs a search against the shared data model, the injected SPL executes with the searcher's permissions, potentially exposing sensitive credentials. This occurs because Splunk Enterprise does not properly neutralize data model calculation fields before including them in generated searches. The issue is fixed in versions 10.4.5, 10.2.9, 10.0.12, and 9.4.17.