EUVD-2026-62957
GHSA-frgf-hh6q-99c3
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Requires valid Splunk login at any non-elevated role (PR:L, AV:N); no availability impact; scope unchanged as container credential exposure is limited.
Primary rating from Vendor (cisco).
CVSS VectorVendor: cisco
Lifecycle Timeline
2DescriptionCVE.org
In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the "admin" or "power" Splunk roles could obtain predictable or default credentials for connected container services. The use of hard-coded credentials is possible because Splunk AI Toolkit generates or stores credentials for connected container services using predictable or hard-coded default values. For more information see Connections tab in the AI Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.7.2/ai-toolkit-commands-macros-and-visualizations/connections-tab-in-the-ai-toolkit) in the Splunk documentation.
AnalysisAI
Hard-coded and predictable credentials in Splunk AI Toolkit versions below 6.0.0 expose connected container services to unauthorized access by any low-privileged Splunk user. The toolkit generates or stores credentials for its container integrations using predictable or fixed default values, which are retrievable through the AI Toolkit Connections tab without requiring elevated Splunk roles. No public exploit has been identified at time of analysis, and no CISA KEV listing exists, but a vendor patch (6.0.0) is available per advisory SVD-2026-0808, reported by Cisco.
Technical ContextAI
Splunk AI Toolkit is an add-on that integrates machine learning container services with the Splunk platform, exposing container orchestration through a Connections tab UI. The affected product is identified by CPE cpe:2.3:a:splunk:splunk_ai_toolkit:*:*:*:*:*:*:*:* covering all versions in the 5.7 line below 6.0.0 (per EUVD-2026-62957). The root cause is CWE-798 (Use of Hard-coded Credentials): rather than generating cryptographically random per-instance credentials for each container service connection, the toolkit uses predictable or fixed default values, storing them in a location accessible to any authenticated Splunk session via the Connections tab. This violates the principle of least-privilege credential isolation and means credential discovery requires no privilege escalation - only UI access.
RemediationAI
Upgrade Splunk AI Toolkit to version 6.0.0 or later, which resolves the hard-coded credential issue per vendor advisory SVD-2026-0808 (https://advisory.splunk.com/advisories/SVD-2026-0808). Prior to patching, rotate credentials for all container services connected through the AI Toolkit Connections tab, as any previously stored predictable credentials should be considered compromised. As a compensating control, restrict which Splunk users have access to the AI Toolkit application and its Connections tab by scoping app permissions to the minimum required user set - this limits who can retrieve the exposed credentials without disabling the toolkit entirely. Additionally, network-segment container services so that direct credential-based access from unexpected source IPs generates security alerts. Patch version 6.0.0 is confirmed available per the vendor advisory but has not been independently verified against a public release manifest.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.
curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or powe
In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet la
In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100,
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through t
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the
A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functional
When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer
A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly re
Same weakness CWE-798 – Use of Hard-coded Credentials
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today