Splunk AI Assistant below 2.0.0: low-privilege users could reach another tenant's data, see indexes outside their scope and change AI settings (CVE-2026-131302 to 131305)
Splunk advisory SVD-2026-1111 (18 November 2026) fixes four authorization flaws in Splunk AI Assistant below 2.0.0. A user without the admin or power role could access data associated with another tenant and have actions attributed to it by sending a client-controlled tenant identifier (CVE-2026-131304), get limited information about indexes and data sources outside their scope through the assistant (CVE-2026-131303), submit feature settings outside the server-side configuration (CVE-2026-131305), and turn on the AI chat training-data consent setting (CVE-2026-131302). Upgrade to 2.0.0.
What it is
CVE-2026-131304 (8.1, CWE-639): the assistant accepted a client-controlled tenant identifier when selecting the authorization context for a REST API request.
CVE-2026-131303 (7.1, CWE-862): the assistant does not fully apply authorization controls to everything it retrieves, so a user could learn limited information about indexes and data sources outside their authorized scope.
CVE-2026-131305 (8.1, CWE-15): the REST API processes client-supplied feature settings without enforcing the server-side configuration boundary, which could modify limited response metadata.
CVE-2026-131302 (4.3, CWE-862): the AI chat training-data consent setting could be switched on through the REST API because that configuration endpoint has no authorization check.
All four need an authenticated Splunk user who does not hold the admin or power role. Splunk lists no exploitation; the issues were found by Splunk's Gabriel Nitu.
How to check
- Check the installed version of the Splunk AI Assistant app on each search head (Apps > Manage Apps). Anything below 2.0.0 is affected.
- Review whether the AI chat training-data consent setting is enabled and who changed it.
How to fix
- Upgrade Splunk AI Assistant to 2.0.0 or later.
- If you can't upgrade yet, Splunk's workaround is to turn off or remove the Splunk AI Assistant app.
# on a search head: find the installed AI Assistant app and its version
grep -ris '^version' $SPLUNK_HOME/etc/apps/*/default/app.conf | grep -i assistant