In Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.8, and 9.4.13, a user who does not hold the "admin" or
Source GCVE Database
Not known to be exploited · CVSS 6.4 Medium · fixed in 10.4.1 : update Splunk Enterprise when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.1, 10.2.6, 10.0.8 +1
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 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.1, 10.2.6, 10.0.8 or 9.4.13.
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
The vulnerability affects Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.8, and 9.4.13. Users should upgrade to these fixed versions or later to remediate the issue. Additionally, enforce strict role definitions and educate users to recognize phishing attempts, as exploitation requires tricking a user into initiating a request. Monitor Splunk documentation on SPL safeguards and role capabilities for best practices.
Description
A vulnerability in Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.8, and 9.4.13 allows a non-admin, non-power user to trick another user into executing arbitrary SPL commands via the Data Model Editor. This occurs because SPL safeguards are not applied when the Data Model Editor runs base searches for auto-extracted fields. Exploitation requires phishing the affected user to initiate a browser request, potentially compromising data confidentiality and system integrity.