Quick answers
- Is CVE-2026-76394 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76394 being exploited in the wild.
- How severe is CVE-2026-76394?
- 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); below 6.0.1 (6.0 branch).
- Is there a fix for CVE-2026-76394?
- A patch was published on 2026-08-19: Fixed in version 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-76394 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-76394?
- 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
This is a missing authorization vulnerability (CWE-862) in Splunk AI Toolkit versions below 6.0.0. Multiple REST API handlers for container and connection management fail to enforce proper authorization checks, allowing low-privileged users to perform privileged operations. The attack vector is network-based and requires only standard user credentials (no admin/power role); no user interaction or additional authentication is needed beyond basic Splunk login. An attacker can start/stop containers, modify configuration data, and access connection credentials. The vulnerability was fixed in version 6.0.0 (for 5.7 branch) and 6.0.1 (for 6.0 branch).
Affected products
- Splunk AI Toolkit below 6.0.0 (5.7 branch); below 6.0.1 (6.0 branch)
Timeline
- 2026-08-19: disclosed
- 2026-08-19: patched: Fixed in version 6.0.0 (5.7 branch) and 6.0.1 (6.0 branch)