CVE-2026-131218: Splunk Enterprise Security · The application generates a query intended to access or manipulate data
Affects Splunk Enterprise SecuritySource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 8.7.0 soon.
Data as of 19 Nov 2026, 20:38 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 8.3 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Splunk Enterprise Security to version 8.7.0 or later, where this vulnerability is fixed. No other mitigations are specified in the vendor advisory.
Description
Splunk Enterprise Security versions prior to 8.7.0 contain a vulnerability in the Mission Control dashboard where users with the mc_investigation_read capability can inject arbitrary Search Processing Language (SPL) into search requests. This injection allows execution of SPL with elevated permissions, enabling unauthorized reading of stored credentials and writing data to indexes and lookups. The issue arises because Mission Control does not validate reserved search filters before incorporating them into dashboard searches. The vulnerability is fixed in version 8.7.0.