The vulnerability is possible because Splunk AI Assistant accepted a client-controlled tenant identifier when selecting the authorization context for a request.
Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
Upgrade Splunk AI Assistant to version 2.0.0 or higher.
Vendor Workaround
Turn off or remove the Splunk AI Assistant. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-1111 |
|
Thu, 19 Nov 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Splunk AI Assistant versions below 2.0.0 a user who does not hold the "admin" or "power" Splunk roles could access data associated with another tenant and cause actions to be attributed to that tenant through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Assistant accepted a client-controlled tenant identifier when selecting the authorization context for a request. | |
| Title | Authorization Bypass through the REST API in Splunk AI Assistant | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: cisco
Published:
Updated: 2026-11-19T20:36:18.712Z
Reserved: 2026-11-17T20:26:14.313Z
Link: CVE-2026-131304
No data.
Status : Received
Published: 2026-11-19T20:17:46.750
Modified: 2026-11-19T20:17:46.750
Link: CVE-2026-131304
No data.
OpenCVE Enrichment
No data.
-
CWE-639
Authorization Bypass Through User-Controlled Key