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