12 matches found
CVE-2026-131304
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...
CVE-2026-131305
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 configuratio...
CVE-2026-131305 Improper Input Validation through the REST API in Splunk AI Assistant
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 configuratio...
EUVD-2026-130570
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 configuratio...
CVE-2026-131305
In Splunk AI Assistant versions below 2.0.0 , a lack of proper input validation allows users without admin or power roles to submit client-controlled feature settings via the REST API . The root cause is the failure of the API to enforce server-side configuration boundaries, which can result in t...
EUVD-2026-130569
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...
CVE-2026-131304
Splunk AI Assistant versions prior to 2.0.0 are vulnerable to an authorization bypass via the REST API . The flaw occurs because the application accepts a client-controlled tenant identifier when determining the authorization context for requests. This allows users without "admin" or "power" role...
CVE-2026-131304 Authorization Bypass through the REST API in Splunk AI Assistant
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...
CVE-2026-131302
In Splunk AI Assistant versions below 2.0.0 , a vulnerability exists where users lacking "admin" or "power" roles can enable the AI chat training-data consent setting. This is caused by missing authorization checks on the affected configuration endpoint of the REST API . No information regarding ...
EUVD-2026-130568
In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could obtain limited information about indexes and data sources outside their authorized scope through the assistant. The vulnerability is possible because Splunk AI Assistant does not fully...
EUVD-2026-130567
In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could turn on the AI chat training-data consent setting through the Representational State Transfer REST API. The missing authorization is possible because the affected configuration endpoint...
CVE-2026-131303
In Splunk AI Assistant versions below 2.0.0 , a vulnerability exists where users lacking admin or power roles can obtain limited information about indexes and data sources outside their authorized scope. The root cause is that the assistant fails to fully apply authorization controls to all retri...