CVE-2026-131213: Splunk Enterprise Security · The software prepares a structured message for communication with another component, but encoding or
Affects Splunk Enterprise SecuritySource CVE Database V5
Not known to be exploited · CVSS 6.7 Medium : upgrade to 8.7.0 when convenient.
Data as of 19 Nov 2026, 20:38 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 6.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:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise Security | Affected
| Fixed in
|
AI-suggested
Upgrade Splunk Enterprise Security to version 8.7.0 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Users should apply this official fix to prevent exploitation.
Description
CVE-2026-131213 is a vulnerability in Splunk Enterprise Security versions before 8.7.0 where an attacker with the 'ess_analyst' role can inject malicious data into finding exclusion rule metadata. This data is not properly escaped, allowing another authenticated user who views the Finding Exclusion Rules page to execute attacker-controlled SPL commands with their permissions. The flaw arises from improper handling of backslashes in the metadata. The issue is fixed in version 8.7.0.