Quick answers
- Is CVE-2026-76396 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76396 being exploited in the wild.
- How severe is CVE-2026-76396?
- High severity, with a CVSS score of 7.5, published 19 August 2026.
- Which products and versions are affected?
- Splunk AI Toolkit below 6.0.0 and 6.0.1.
- Is there a fix for CVE-2026-76396?
- A patch was published on 2026-08-19: Fixed in versions 6.0.0 (base 5.7) and 6.0.1 (base 6.0) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76396 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-76396?
- 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 issue (CWE-269) in Splunk AI Toolkit versions below 6.0.0 and 6.0.1. The apply search command, which deserializes and loads model files, is not marked as risky, allowing users with the schedule_search capability to invoke it in scheduled searches without proper authorization checks. An authenticated user with schedule_search privileges can craft a scheduled search that loads a malicious or unauthorized model file, achieving remote code execution or data exfiltration. The issue has been patched in versions 6.0.0 (for base 5.7) and 6.0.1 (for base 6.0).
Affected products
- Splunk AI Toolkit below 6.0.0 and 6.0.1
Timeline
- 2026-08-19: disclosed
- 2026-08-19: patched: Fixed in versions 6.0.0 (base 5.7) and 6.0.1 (base 6.0)