Skip to main content
CVE-2026-131215VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131215· 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

Splunk Enterprise Security versions 8.7.0 and later include fixes for this vulnerability. Users should upgrade to version 8.7.0 or later to remediate this issue. Until then, restrict the ueba_finding_exclusion_edit capability to trusted users only. No vendor advisory or patch links were provided in the input; therefore, confirm patch availability and remediation details from official Splunk documentation or support.

Description

In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where users with the ueba_finding_exclusion_edit capability can inject attacker-controlled values into UEBA finding exclusion rules. These values are not properly escaped before being used in generated Search Processing Language (SPL) commands, which are executed with elevated permissions. This allows the user to execute arbitrary SPL commands that can read stored credentials and modify lookups and knowledge objects.

References

Community reviews

Loading reviews…