CVE-2026-131304

Authorization Bypass through the REST API in Splunk AI Assistant

Published Nov 19, 2026 CVSS 3.1 · 8.1 High EPSS n/a KEV · Not listed
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.

Analysis

No analysis available yet

Remediation

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.

Advisories

No advisories available
History
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

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

Subscriptions

No data.

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
cisco
Published
Updated
Nov 19, 2026, 8:36 PM
Reserved
Nov 17, 2026, 8:26 PM
Status
Received
Published
Nov 19, 2026, 8:17 PM
Modified
Nov 19, 2026, 8:17 PM