CVE-2026-131233: 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 5.4 Medium : upgrade to 8.7.0 when convenient.
Data as of 19 Nov 2026, 20:40 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.4 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:NExploitation 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 or workaround is indicated by the vendor advisory. Users should ensure that only trusted roles have the run_collect capability and restrict access to the Time Center dashboard to minimize risk.
Description
CVE-2026-131233 is a vulnerability in Splunk Enterprise Security versions prior to 8.7.0 where users with the run_collect capability can inject attacker-controlled values into endpoint summary data. When another user with access to the Time Center dashboard selects an affected row, the system may execute attacker-controlled SPL commands with the selecting user's permissions. This occurs because the Time Center dashboard does not properly escape endpoint summary values before using them in drilldown searches. The issue was fixed in version 8.7.0.