Quick answers
- Is CVE-2026-76392 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76392 being exploited in the wild.
- How severe is CVE-2026-76392?
- Medium severity, with a CVSS score of 5.4, published 19 August 2026.
- Which products and versions are affected?
- Splunk AI Toolkit Below 6.0.0 (5.7.x and earlier), Below 6.0.1 (6.0.x).
- Is there a fix for CVE-2026-76392?
- 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-76392 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-76392?
- 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 vulnerability (CVE-2026-76392) stems from the use of hard-coded or predictable default credentials when Splunk AI Toolkit generates or stores credentials for connected container services. The vulnerability resides in the Connections tab functionality. An attacker without "admin" or "power" Splunk roles can discover these credentials through the UI or REST API, potentially gaining unauthorized access to backend container services. The vulnerability requires network access to the Splunk instance and authentication as a non-privileged Splunk user. Patched in versions 6.0.0 and later (6.0.1 for the 6.0 branch).
Affected products
- Splunk AI Toolkit Below 6.0.0 (5.7.x and earlier), Below 6.0.1 (6.0.x)
Timeline
- 2026-08-19: disclosed