Container credential disclosure via predictable defaults
Published Aug 19, 2026 · Updated Aug 19, 2026
Hard-coded credentials in Splunk AI Toolkit before 6.0.0 allow remote authenticated users to obtain container service credentials. The app generates or stores credentials for connected container services using predictable or hard-coded default values. A Splunk account below the admin and power roles is sufficient, exposing credentials that permit access to the connected services.
Summary
What happened
Hard-coded credentials in Splunk AI Toolkit before 6.0.0 allow remote authenticated users to obtain container service credentials. The app generates or stores credentials for connected container services using predictable or hard-coded default values. A Splunk account below the admin and power roles is sufficient, exposing credentials that permit access to the connected services.
The record
- CVE
- CVE-2026-76392
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- Splunk, Inc.
- Product
- Splunk AI Toolkit
- Classifications
- CWE-798, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 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.
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