CVE-2026-131304Splunk AI Assistant Authorization Bypass Through User-Controlled Key
NVD
Vulnerability Summary
Authorization Bypass through the REST API in Splunk AI Assistant. 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.
CVSS v3.1 Base Metrics — Score 8.1 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
Affected & Patched Versions
- Splunk AI Assistant before 2.0.0
- Upgrade Splunk AI Assistant to version 2.0.0 or higher.
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is high.
- Check whether you run Splunk AI Assistant and which version.
- Update to a patched version listed above, then confirm the new version.
- Until you can update, follow the vendor workaround: Turn off or remove the Splunk AI Assistant. For more information see Manage app and add-on objects in the Splunk documentation.
Timeline
- Nov 19, 2026Published
- Nov 19, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Splunk AI Assistant CVEsYou are reading CVE-2026-131304. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore Splunk AI Assistant CVEs
External References
- Vendor Advisoryhttps://advisory.splunk.com/advisories/SVD-2026-1111
Data last checked: Nov 19, 2026 02:08 UTC