Skip to main content
VulnerabilityPublished

CVE-2026-131215: Splunk Enterprise Security · The software constructs all or part of a command, data structure, or record using

Affects Splunk Enterprise SecuritySource CVE Database V5

0
Compare

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

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

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

Description

CVE-2026-131215 is a high-severity vulnerability in Splunk Enterprise Security versions prior to 8.7.0. It allows users with the ueba_finding_exclusion_edit capability to inject attacker-controlled values into UEBA finding exclusion rules. These values are not properly escaped before being used in Search Processing Language (SPL) commands, enabling execution of SPL commands with elevated permissions. This can lead to unauthorized reading of stored credentials and modification of lookups and knowledge objects. The issue is fixed in version 8.7.0.

References

Community reviews

Loading reviews…