Description
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.
Published: 2026-08-19
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Splunk AI Toolkit versions prior to 6.0.0 generate or store credentials for connected container services using predictable or hard‑coded values. Users with non‑admin or power roles can read these credentials, which can then be used to access the container services directly. This flaw allows attackers to gain unauthorized access to external container endpoints that are intended to be protected by proper authentication mechanisms, potentially leading to further compromise if those containers host sensitive data or services.

Affected Systems

The vulnerability affects the Splunk AI Toolkit application across all installations where the version is older than 6.0.0. Any deployment of this application that connects to external container services is potentially impacted, regardless of the overall Splunk installation version.

Risk and Exploitability

The flaw carries a CVSS score of 5.4, indicating a moderate severity. No EPSS score is available, and the vulnerability is not listed in the CISA KEV catalog. Based on the description, the likely attack vector is through the Splunk web interface or API where the AI Toolkit is accessed, or by directly interacting with the AI Toolkit’s stored configuration. An attacker with read permissions to the application configuration can obtain the default credentials and then authenticate to the target container services, potentially escalating privileges or exfiltrating data. While no public exploit is documented, the use of hard‑coded credentials presents a clear avenue for credential abuse when combined with knowledge of the container service endpoints.

Generated by OpenCVE AI on August 20, 2026 at 08:20 UTC.

Remediation

Vendor Solution

Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status.


Vendor Workaround

Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation.


OpenCVE Recommended Actions

  • Upgrade the Splunk AI Toolkit to version 6.0.0 or later to eliminate the use of hard‑coded credentials
  • If an upgrade cannot be performed immediately, disable or remove the AI Toolkit application to prevent its use of default credentials
  • Update all container service endpoints to use unique, strong authentication credentials and audit existing configurations to confirm that no hard‑coded values remain

Generated by OpenCVE AI on August 20, 2026 at 08:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 26 Aug 2026 21:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 21 Aug 2026 19:00:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:splunk:ai_toolkit:*:*:*:*:*:*:*:*

Thu, 20 Aug 2026 00:45:00 +0000

Type Values Removed Values Added
First Time appeared Splunk
Splunk ai Toolkit
Vendors & Products Splunk
Splunk ai Toolkit

Wed, 19 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Use of Hard-coded Credentials in Container Connections in Splunk AI Toolkit
Weaknesses CWE-798
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}


Subscriptions

Splunk Ai Toolkit
cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

Updated: 2026-08-26T19:35:04.238Z

Reserved: 2026-08-19T12:02:03.631Z

Link: CVE-2026-76392

cve-icon Vulnrichment

Updated: 2026-08-26T19:34:37.517Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-19T22:17:25.613

Modified: 2026-08-26T20:18:00.803

Link: CVE-2026-76392

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-20T08:30:04Z

Weaknesses
  • CWE-798

    Use of Hard-coded Credentials