In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could turn
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.0.0 when convenient.
Data as of 19 Nov 2026, 22:20 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 4.3 |
|---|
- Patch
- Available – fixed in 2.0.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 AI Assistant to 2.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk AI Assistant | Affected
| Fixed in
|
AI-suggested
Until then, restrict access to the REST API endpoints to trusted users and monitor for vendor advisories for official remediation guidance.
Description
Splunk AI Assistant versions below 2.0.0 contain a vulnerability where users without 'admin' or 'power' roles can enable the AI chat training-data consent setting via the REST API due to missing authorization checks on the configuration endpoint.