Skip to main content
CVE-2026-131210VulnerabilityPublished

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-131210· High 8.1

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

Data as of 19 Nov 2026, 22:48 UTC

CVSS 3.1 base score
8.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.18.1
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: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

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. Until then, restrict roles from having both ueba_finding_exclusion_edit capability and write access to globally shared lookup definitions to reduce risk.

Description

Splunk Enterprise Security versions below 8.7.0 contain a vulnerability where users with the ueba_finding_exclusion_edit capability and write access to globally shared lookup definitions can create finding exclusion rules referencing attacker-controlled lookups. This leads to arbitrary Search Processing Language (SPL) command execution with elevated permissions, potentially exposing stored credentials and data beyond assigned role permissions. The issue arises because UEBA finding exclusion processing does not properly quote lookup names in SPL searches.

References

Community reviews

Loading reviews…