Skip to main content
CVE-2026-131198VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131198· High 7.1

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

Data as of 19 Nov 2026, 22:49 UTC

CVSS 3.1 base score
7.1High
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.17.1
Patch
Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

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_view_im_data capability to trusted users only and monitor for unusual activity related to the Mission Control incident mapping REST API.

Description

In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with a role possessing the mc_view_im_data capability can exploit the Mission Control incident mapping REST API to execute arbitrary Search Processing Language (SPL) commands with elevated permissions. This occurs because the API does not validate incident identifiers before incorporating them into SPL searches. Exploitation could lead to exposure of all data in Splunk indexes, stored credentials, and unauthorized modification of protected indexes and lookup data.

References

Community reviews

Loading reviews…