EUVD-2026-62959
GHSA-6w69-87j9-3r87
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
Network-accessible REST API requires only a low-privileged account; high I/A from container control; limited confidentiality impact from configuration data exposure only.
Primary rating from Vendor (cisco).
CVSS VectorVendor: cisco
Lifecycle Timeline
3DescriptionCVE.org
In Splunk AI Toolkit versions below 6.0.0, a low-privileged user who does not hold the "admin" or "power" Splunk roles could start, stop, and configure containers, and read or modify connection and configuration data through the Representational State Transfer (REST) API. The missing authorization is possible because multiple REST API handlers in Splunk AI Toolkit do not enforce authorization checks. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation.
AnalysisAI
Missing authorization checks across multiple REST API handlers in Splunk AI Toolkit versions below 6.0.0 allow any low-privileged authenticated Splunk user - one who holds neither the 'admin' nor 'power' role - to start, stop, and reconfigure containers and to read or modify sensitive connection and configuration data. The vulnerability stems from CWE-862 (Missing Authorization), where the REST endpoints simply omit role-based access enforcement rather than incorrectly implementing it. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the low attack complexity and the fact that it was reported by Cisco make it a credible near-term target.
Technical ContextAI
Splunk AI Toolkit (CPE: cpe:2.3:a:splunk:splunk_ai_toolkit:*:*:*:*:*:*:*:*) is an add-on to the Splunk platform that integrates machine learning capabilities, including containerized workloads for running ML models. The toolkit exposes a REST API surface consistent with Splunk's standard SPL-backed HTTP handler architecture. The root cause is CWE-862 (Missing Authorization): the REST API handlers responsible for container lifecycle management and configuration operations were implemented without inserting authorization gate checks against Splunk's role hierarchy. This means the Splunk authentication layer correctly identifies the caller, but the handlers proceed regardless of whether that caller holds a privileged role. Affected versions span the 5.7 line up to (but not including) the 6.0.0 release.
RemediationAI
The primary remediation is to upgrade Splunk AI Toolkit to version 6.0.0 or later, where the REST API handlers have been updated to enforce authorization checks consistent with Splunk's role-based access model. The vendor advisory at https://advisory.splunk.com/advisories/SVD-2026-0808 should be consulted for the authoritative upgrade path. As a compensating control pending upgrade, administrators should audit which user accounts hold any level of Splunk authentication and consider temporarily restricting API access to the AI Toolkit REST endpoints via Splunk's network-level access controls or firewall rules - noting that this may break legitimate ML workflow integrations. Restricting the REST API surface to only admin and power role holders at the Splunk tier, if the platform permits such interim configuration, would also limit exposure. No workaround eliminates the underlying authorization gap without the patch.
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-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today