Quick answers
- Is CVE-2026-76391 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76391 being exploited in the wild.
- How severe is CVE-2026-76391?
- High severity, with a CVSS score of 8.3, published 19 August 2026.
- Which products and versions are affected?
- Splunk AI Toolkit below 6.0.0 (5.7 branch) and below 6.0.1 (6.0 branch).
- Is there a fix for CVE-2026-76391?
- A patch was published on 2026-08-19: Fixed in versions 6.0.0 (5.7 branch) and 6.0.1 (6.0 branch) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76391 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-76391?
- 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 privilege management issue (CWE-863) in the Agent Run History handler. The flaw occurs because the handler improperly replaces the calling user's session key with a system authentication token before performing search operations, effectively bypassing role-based access controls. The vulnerability requires network access to the Splunk instance but no special preconditions beyond being a Splunk user. An authenticated attacker can leverage this to execute arbitrary searches with elevated privileges, access sensitive data, and manipulate or delete search jobs from other users. Fixed in versions 6.0.0 for the 5.7 branch and 6.0.1 for the 6.0 branch.
Affected products
- Splunk AI Toolkit below 6.0.0 (5.7 branch) and below 6.0.1 (6.0 branch)
Timeline
- 2026-08-19: disclosed
- 2026-08-19: patched: Fixed in versions 6.0.0 (5.7 branch) and 6.0.1 (6.0 branch)