CVE-2026-76391: Improper Privilege Management through Agent Run History in Splunk AI Toolkit
In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the "admin" or "power" Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk AI Toolkitto a version that resolves this vulnerability.Fixed in 6.0.0
Event History
Frequently Asked Questions
Which users are exposed to this issue?
Users who do not have the Splunk "admin" or "power" roles may be able to exploit the issue through Agent Run History. The affected behavior can allow those users to run searches with system-level privileges and interact with other users' search jobs.
What access does an attacker need?
An attacker needs access as a Splunk user without the "admin" or "power" role. No user interaction is required.
What could an attacker do?
An attacker could access all relevant data, affect system integrity, and read or delete search jobs belonging to other users. This occurs because the Agent Run History handler uses a system authentication token before performing search operations.
Which versions are affected?
Splunk AI Toolkit versions below 6.0.0 are affected.