In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability
Source GCVE Database
Not known to be exploited · CVSS 4.2 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 | 4.2 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:LExploitation 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 issue is resolved. No other mitigation or workaround is documented. Since this is a product vulnerability fixed in a later version, applying the official update is the recommended remediation.
Description
In Splunk Enterprise Security versions below 8.7.0, users with the mc_investigation_read capability can overwrite Mission Control preference records of other users, potentially removing saved filters and analyst queue settings. This occurs because the Mission Control REST API does not properly bind authorization checks to preference record updates. Exploitation requires knowledge of a preference record identifier not normally exposed to the user, limiting the ease of exploitation.