In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the edit_modinput_data_migrator
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium : upgrade to 8.7.0 when convenient.
Data as of 19 Nov 2026, 22:54 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.5 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 19 Nov 2026.
What to do
Upgrade Splunk Enterprise Security to 8.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise Security | Affected
| Fixed in
|
AI-suggested
Upgrade to Splunk Enterprise Security version 8.7.0 or later where this vulnerability is addressed. Until then, restrict assignment of the edit_modinput_data_migrator capability to trusted users only.
Description
Splunk Enterprise Security versions below 8.7.0 contain a vulnerability where users with the edit_modinput_data_migrator capability can execute arbitrary Search Processing Language (SPL) commands with elevated permissions. This allows reading data beyond their role scope and writing data to indexes and lookup tables. The issue arises because the data migration input does not restrict searches to only product-supplied migration tasks before execution.