Skip to main content
CVE-2026-131218VulnerabilityPublished

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131218· High 8.3

Not known to be exploited · CVSS 8.3 High : upgrade to 8.7.0 soon.

Data as of 19 Nov 2026, 22:39 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (cisco)CVSS 3.18.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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
SplunkSplunk Enterprise SecurityAffected
  • <8.7.0
Fixed in
  • 8.7.0

AI-suggested

If you cannot patch yet, restrict roles with the mc_investigation_read capability to trusted users only and monitor for any unusual activity related to Mission Control dashboard searches.

Description

Splunk Enterprise Security versions below 8.7.0 contain a vulnerability where users with the mc_investigation_read capability can inject arbitrary Search Processing Language (SPL) into Mission Control dashboard searches. This injection allows Mission Control to execute SPL with elevated permissions, potentially enabling the 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.

References

Community reviews

Loading reviews…