What happened
In Splunk AI Assistant below 2.0.0, a non-admin/non-power user can access data associated with another tenant and cause actions to be attributed to that tenant via the REST API because the assistant accepted a client-controlled tenant identifier when choosing the authorization context.
Why it matters
The assistant is the AI analysis surface over Splunk data; forcing a tenant identifier lets a low-privileged user read another tenant's indexed data and misattribute AI-driven actions — a cross-tenant authorization violation in an AI analytics product.
Attack vector
Splunk AI Assistant accepted a client-controlled tenant identifier when selecting the authorization context for a request, so a low-privileged user can select another tenant's context and read its data or have actions attributed to it. CWE-639, CVSS 3.1 8.1.
Affected systems
Splunk AI Assistant < 2.0.0 (REST API)
Mitigation
Upgrade Splunk AI Assistant to 2.0.0 or later (see SVD-2026-1111).