In Splunk AI Assistant versions below 2.0.0 a user who does not hold the "admin" or "power" Splunk roles could access
Source GCVE Database
Not known to be exploited · CVSS 8.1 High : upgrade to 2.0.0 soon.
Data as of 19 Nov 2026, 22:19 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 8.1 |
|---|
- Patch
- Available – fixed in 2.0.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 AI Assistant to 2.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk AI Assistant | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict access to trusted users and monitor for unusual cross-tenant activity if possible.
Description
Splunk AI Assistant versions below 2.0.0 contain a vulnerability where users without admin or power roles can access data from other tenants and perform actions attributed to those tenants via the REST API. This occurs because the software accepts a client-controlled tenant identifier for authorization context selection.