Cross-user history access and deletion via scope loss
Published Aug 19, 2026 · Updated Aug 20, 2026
Access control flaw in Splunk AI Toolkit 5.7 before 6.0.0 allows remote authenticated users with the power role to read or delete experiment history. Experiment-history REST processing fails to preserve the trusted experiment scope and uses caller-controlled query values to select restricted records. A power-role account is required; successful requests disclose or delete other users' experiment-history data without interrupting service.
Summary
What happened
Access control flaw in Splunk AI Toolkit 5.7 before 6.0.0 allows remote authenticated users with the power role to read or delete experiment history. Experiment-history REST processing fails to preserve the trusted experiment scope and uses caller-controlled query values to select restricted records. A power-role account is required; successful requests disclose or delete other users' experiment-history data without interrupting service.
The record
- CVE
- CVE-2026-76397
- Published
- Aug 19, 2026
- Updated
- Aug 20, 2026
- Vendor
- Splunk, Inc.
- Product
- Splunk AI Toolkit
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.7 <6.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo