Authorization Bypass through the REST API in Splunk AI Assistant
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Splunk | Splunk AI Assistant | affected |
|
No data.
No data.
No data available yet.
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.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-1111 |
|
| 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
|
No data.