EUVD-2026-62963
GHSA-cq72-pxmj-w4mh
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Network-accessible REST API requires only low-privilege authentication; impact is limited to integrity of experiment records with no confidentiality or availability effect.
Primary rating from Vendor (cisco).
CVSS VectorVendor: cisco
Lifecycle Timeline
2DescriptionCVE.org
In Splunk AI Toolkit versions below 6.0.1, a user who does not hold the "admin" or "power" Splunk roles could delete the experiment history of another user without permission through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Toolkit deletes experiment history before it verifies that the user can delete the associated experiment. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.
AnalysisAI
Missing authorization in Splunk AI Toolkit below version 6.0.1 allows any authenticated low-privilege user to delete the experiment history belonging to another user via the REST API. The root cause is a sequencing flaw: the Toolkit executes the deletion operation before verifying whether the requesting user holds permission to delete the target experiment, violating the principle of check-before-act. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog; however, a patch is available in version 6.0.1.
Technical ContextAI
Splunk AI Toolkit is an add-on for the Splunk platform that provides machine-learning and AI-assisted experiment workflows; the affected component is its REST API layer for managing experiment history. The CWE-862 (Missing Authorization) root cause reflects a time-of-check/time-of-use-style authorization bypass: the delete operation completes prior to the authorization gate executing, meaning the permission check is effectively dead code for the deletion path. The affected CPE is cpe:2.3:a:splunk:splunk_ai_toolkit:*:*:*:*:*:*:*:*, encompassing all toolkit versions below 6.0.1 as confirmed by EUVD listing EUVD-2026-62963. Splunk roles ('admin' and 'power') are the intended gatekeepers for this operation, but the sequencing flaw bypasses that gate entirely for lower-privilege roles.
RemediationAI
Upgrade Splunk AI Toolkit to version 6.0.1 or later, which corrects the authorization sequencing flaw by verifying user permissions before executing the deletion operation. The vendor advisory is published at https://advisory.splunk.com/advisories/SVD-2026-0808. If immediate patching is not possible, a compensating control is to restrict REST API access at the network layer (firewall or Splunk network ACLs) to only trusted hosts, and to audit low-privilege role assignments to minimize the number of accounts that could trigger the flaw. Note that restricting API access broadly may affect legitimate Splunk integrations and should be evaluated against operational needs. Role-based reviews alone are insufficient as a workaround because any valid low-privilege account can exploit the flaw.
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