CVE-2026-131305

Splunk AI Assistant could accept client-controlled feature settings

Splunk · Splunk AI Assistant

First documented disclosure · Review checkpoint

Summary

A non-admin user could alter limited response metadata through feature settings.

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.

Exploitation evidence source

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 accepted feature configuration without enforcing its server-side boundary.

Conditions required

An authenticated Splunk user without the admin or power roles can access the affected REST API.

Potential impact

Limited response-metadata modification; the description does not establish arbitrary data access.

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