CVE-2026-131304
Splunk AI Assistant could use a caller-selected tenant context
Splunk · Splunk AI Assistant
First documented disclosure · Review checkpoint
Summary
A user could access another tenant’s data and have actions attributed to it.
Severity and exploitation evidence
High · 8.1/10 · CVSS 3.1. Severity source.
Exploitation not established: Reviewed public sources describe the weakness, a correction or a controlled demonstration; malicious exploitation against users is not established.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The REST API trusted a client-supplied tenant identifier when choosing authorization context.
Conditions required
An authenticated Splunk user without the admin or power roles can access the affected REST API.
Potential impact
Cross-tenant information access and incorrect action attribution.
Affected versions and configurations
Before 2.0.0.
Fix and mitigation status
2.0.0.
Practical next steps
Upgrade to 2.0.0 or later; turn off or remove the assistant until then.
Operating lesson
Enforce tenant, role and configuration boundaries at every assistant API.
Evidence and limits
The original vendor bulletin predates the November 19 CNA ingestion. Each CVE has its own stated impact; no cross-tenant impact is inherited by the limited-metadata issue. CNA publication is 2026-11-19; this is distinct from the earliest reviewed public source and correction dates. cisco assessments: CVSS 3.1 8.1.
Sources
- cisco CVE authority record
Primary source ·
- Splunk SVD-2026-1111
Primary source ·