# CVE-2026-76397: Splunk AI Toolkit improper access control in experiment history

Source: https://junglewise.ai/threats/cve-2026-76397-splunk-ai-toolkit-improper-access-control-in-experiment-history  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-19. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-76397 · Severity: high · CVSS 8.1 · Published 2026-08-19

Splunk AI Toolkit versions before 6.0.0 contain an access control flaw that allows users with the "power" role to view and delete experiment history data belonging to other users. This bypasses the intended data isolation and could result in unauthorized data destruction, loss of audit trails, and disruption of machine learning workflows across the organization.

Technologies: [Splunk AI Toolkit](https://junglewise.ai/threats/technologies/ai-toolkit). Vendors: [Splunk](https://junglewise.ai/threats/vendors/splunk).

## Quick answers

**Is CVE-2026-76397 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-76397 being exploited in the wild.

**How severe is CVE-2026-76397?** High severity, with a CVSS score of 8.1, published 19 August 2026.

**Which products and versions are affected?** Splunk AI Toolkit below 6.0.0.

**Is there a fix for CVE-2026-76397?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-76397 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-76397?** Check whether you run Splunk AI Toolkit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an improper access control flaw (CWE-639) in the experiment history REST API endpoint. The root cause is that Splunk AI Toolkit fails to preserve the trusted experiment scope when processing caller-controlled query values before accessing restricted history data. An attacker with the "power" Splunk role can craft malicious requests to the REST API to access and delete experiment history records associated with other users. No special preconditions beyond holding the "power" role are required. The fix is available in version 6.0.0 for the 5.7 branch and version 6.0.1 for the 6.0 branch.

## Affected products

- Splunk AI Toolkit below 6.0.0

## Timeline

- 2026-08-19: disclosed

## References

- [https://advisory.splunk.com/advisories/SVD-2026-0808](https://advisory.splunk.com/advisories/SVD-2026-0808)

## Related threats

- [Splunk AI Toolkit incorrect permission assignment for scheduled searches](https://junglewise.ai/threats/cve-2026-76399-splunk-ai-toolkit-incorrect-permission-assignment-for-scheduled)
- [Splunk AI Toolkit improper access control in experiment history deletion](https://junglewise.ai/threats/cve-2026-76398-splunk-ai-toolkit-improper-access-control-in-experiment-history)
- [Splunk AI Toolkit improper access control in scheduled searches](https://junglewise.ai/threats/cve-2026-76396-splunk-ai-toolkit-improper-access-control-in-scheduled-searches)
- [Splunk AI Toolkit RCE through unsafe model deserialization](https://junglewise.ai/threats/cve-2026-76395-splunk-ai-toolkit-rce-through-unsafe-model-deserialization)
- [Splunk AI Toolkit missing authorization in REST API container management](https://junglewise.ai/threats/cve-2026-76394-splunk-ai-toolkit-missing-authorization-in-rest-api-container)