The vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary.
Metrics
Affected Vendors & Products
No advisories yet.
Solution
Upgrade Splunk AI Assistant to version 2.0.0 or higher.
Workaround
Turn off or remove the Splunk AI Assistant. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation.
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-1111 |
|
Thu, 19 Nov 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could submit client-controlled feature settings through the Representational State Transfer (REST) API. This could modify limited response metadata outside the expected server-side configuration. The vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary. | |
| Title | Improper Input Validation through the REST API in Splunk AI Assistant | |
| Weaknesses | CWE-15 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: cisco
Published:
Updated: 2026-11-19T19:56:49.032Z
Reserved: 2026-11-17T20:26:14.313Z
Link: CVE-2026-131305
No data.
Status : Received
Published: 2026-11-19T20:17:46.870
Modified: 2026-11-19T20:17:46.870
Link: CVE-2026-131305
No data.
OpenCVE Enrichment
No data.