Skip to main content
CVE-2026-131213VulnerabilityPublished

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131213· Medium 6.7

Not known to be exploited · CVSS 6.7 Medium : upgrade to 8.7.0 when convenient.

Data as of 19 Nov 2026, 22:49 UTC

CVSS 3.1 base score
6.7Medium
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.16.7
Patch
Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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

Since the vulnerability affects versions below 8.7.0, upgrading to version 8.7.0 or later is implied as a remediation step. Users should consult the official Splunk Enterprise Security documentation and advisories for confirmed patch availability and apply updates accordingly.

Description

A vulnerability in Splunk Enterprise Security versions below 8.7.0 allows a user with the "ess_analyst" role to store attacker-controlled data in finding exclusion rule metadata. When another authenticated user opens the Finding Exclusion Rules page, Splunk Enterprise Security may execute attacker-controlled Search Processing Language (SPL) commands with the permissions of that user. This occurs because backslashes in the metadata are not properly escaped before being added to a page search.

References

Community reviews

Loading reviews…