In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could trick a user that holds a role with
Source GCVE Database
Not known to be exploited · CVSS 5.0 Medium : upgrade to 8.7.0 when convenient.
Data as of 19 Nov 2026, 22:49 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.0 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/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
Since the vulnerability requires phishing and user interaction, organizations should educate users with the ueba_can_view_ui capability to be cautious about opening unsolicited links. Monitor vendor advisories for official patches or updates addressing this issue.
Description
In Splunk Enterprise Security versions below 8.7.0, an unauthenticated attacker can craft a malicious link to the User and Entity Behavior Analytics (UEBA) Overview dashboard. If a user with the ueba_can_view_ui capability opens this link, attacker-controlled Search Processing Language (SPL) commands may execute with that user's permissions. This can lead to exposure or modification of data accessible to the user and partial disruption of search processing. Exploitation requires phishing the user to open the malicious link. The vulnerability arises because the dashboard does not properly escape filter values before inserting them into SPL searches.