Skip to main content
CVE-2026-131199VulnerabilityPublished

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-131199· High 8.8

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

Data as of 19 Nov 2026, 22:53 UTC

CVSS 3.1 base score
8.8High
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.8
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:H

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

A fix is available in Splunk Enterprise Security version 8.7.0 and later. Users should upgrade to version 8.7.0 or above to remediate this vulnerability. No additional mitigations are specified in the vendor documentation. Until upgrading, restrict roles with mc_investigation_read capability to trusted users only.

Description

In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists in the Risk Event Timeline REST API that allows users with the mc_investigation_read capability to execute arbitrary SPL commands with elevated permissions. This flaw arises because the API fails to validate request inputs before incorporating them into search macro arguments. Exploitation could lead to exposure of stored credentials and unauthorized modification of indexes and lookup data.

References

Community reviews

Loading reviews…