CVE-2026-76397: Improper Access Control in Experiment History through the REST API in Splunk AI Toolkit
In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.
Affected Software
Event History
Frequently Asked Questions
Which users are exposed to this issue?
Users assigned the Splunk "power" role are able to access and delete relevant experiment-history data belonging to other users. The issue affects Splunk AI Toolkit versions below 6.0.0.
What does an attacker need to exploit the vulnerability?
The attacker needs an authenticated Splunk account with the "power" role. No user interaction is required, and exploitation is performed through the REST API using caller-controlled query values.
Are confidentiality and integrity affected?
Yes. A successful attacker can read experiment-history data associated with other users and delete that data. The supplied vector indicates no availability impact.
What is the immediate mitigation if upgrading is not possible?
The provided information identifies the "power" role as the required privilege. Restrict assignment of that role to trusted users until affected deployments can be upgraded to version 6.0.0 or later.