Splunk AI Assistant authorization bypass in REST API tenant selection
Affects Splunk AI Assistant versions below 2.0.0 where a user without the admin or power roles can reach another tenant's data through the REST API. Fixed in 2.0.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.0
- Who is exposed
- Specific setups only
Summary
Written by a model
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.
Who should check
Teams running Splunk AI Assistant below version 2.0.0 on Splunk Enterprise deployments with REST API access for low-privileged users
“In Splunk AI Assistant versions below 2.0.0 a user who does not hold the "admin" or "power" Splunk roles”
What to do
Check whether your setup matches what the bug needs.
Splunk AI Assistant versions below 2.0.0 Splunk AI Assistant accepted a client-controlled tenant identifier when selecting the authorization context for a requestUpgrade to a fixed version: 2.0.0.
Workaround: Turn off or remove the Splunk AI Assistant.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131304 (Authorization Bypass through the REST API in Splunk AI Assistant), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131304 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk AI Assistant: fixed in 2.0.0
Fixed versions: 2.0.0.
Conditions (all must be true for the bug to be hit):
- Splunk AI Assistant versions below 2.0.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1111)
- Splunk AI Assistant accepted a client-controlled tenant identifier when selecting the authorization context for a request (source: https://advisory.splunk.com/advisories/SVD-2026-1111)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Turn off or remove the Splunk AI Assistant. (source: https://www.cve.org/CVERecord?id=CVE-2026-131304)
CISA KEV: CVE-2026-131304 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131304 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1111
- https://www.cve.org/CVERecord?id=CVE-2026-131304
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131304
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131304"}.Affected versions
- Splunk Splunk AI Assistantfixed in 2.0.0
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1111 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131304 |
| Record | NVD · CVE-2026-131304 |
Questions about CVE-2026-131304
Is CVE-2026-131304 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Splunk AI Assistant accepted a tenant identifier chosen by the client when selecting the authorization context for a request. A user without the admin or power role could therefore access data belonging to another tenant and cause actions to be attributed to that tenant.
Source: advisory.splunk.com, cve.org
Which versions are affected by CVE-2026-131304?
Splunk AI Assistant: before 2.0.0.
Source: cve.now feed data
Am I affected, and how do I check?
The advisory says versions of Splunk AI Assistant below 2.0.0 are affected, and the issue concerns users who do not hold the admin or power Splunk roles. To check a version, look at the installed version of Splunk AI Assistant in the Splunk app management page.
Source: advisory.splunk.com, cve.org
How do I fix CVE-2026-131304?
Upgrade Splunk AI Assistant to version 2.0.0 or higher. If an upgrade is not possible, the advisory's workaround is to turn off or remove the Splunk AI Assistant.
Source: advisory.splunk.com, cve.org
Related
- CVE-2026-131305Improper Input Validation through the REST API in Splunk AI Assistant
- CVE-2026-131303Missing Authorization through the REST API in Splunk AI Assistant
- CVE-2026-131302Missing Authorization in AI Chat Settings through the REST API in Splunk AI Assistant
- CVE-2026-131287Remote Code Execution (RCE) through the REST API in Splunk SOAR
- CVE-2026-131295Improper Authorization in Playbook Execution in Splunk SOAR
- CVE-2026-131293Improper Access Control in the Data Management Automation API in Splunk SOAR
No corrections so far. Something wrong on this page? Report an error.