Skip to main content
VulnerabilityPublished

CVE-2026-131198: Splunk Enterprise Security · The product does not validate or incorrectly validates input that can affect the control flow or data

Affects Splunk Enterprise SecuritySource CVE Database V5

0
Compare

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

Data as of 19 Nov 2026, 20:36 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

Upgrade Splunk Enterprise Security to version 8.7.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated by the vendor advisory.

Description

CVE-2026-131198 is a vulnerability in Splunk Enterprise Security versions before 8.7.0. It allows users with the mc_view_im_data capability to execute arbitrary SPL commands with elevated permissions via the Mission Control incident mapping REST API. This occurs because the API does not properly validate incident identifiers before incorporating them into SPL searches. Exploitation could lead to exposure of all data in Splunk indexes, stored credentials, and modification of protected indexes and lookup data. The issue is fixed in version 8.7.0.

References

Community reviews

Loading reviews…