EUVD-2026-62962
GHSA-q3cf-x2fg-gv4f
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Network-accessible Splunk endpoint; 'power' role required (PR:L); IDOR enables full read/delete of peer experiment data (C:H/I:H) with no availability impact (A:N).
Primary rating from Vendor (cisco).
CVSS VectorVendor: cisco
Lifecycle Timeline
3DescriptionCVE.org
In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. 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
Unauthorized cross-user data access and deletion in Splunk AI Toolkit below 6.0.0 allows any authenticated user holding the 'power' Splunk role to read and destroy experiment history records belonging to other users. The root cause is CWE-639 (IDOR): the toolkit fails to preserve a trusted experiment scope boundary when processing caller-controlled query values, enabling horizontal privilege escalation across all experiment history without touching admin-level permissions. No active exploitation or public exploit code has been identified at time of analysis; a vendor-released patch (6.0.0) is available per Splunk advisory SVD-2026-0808.
Technical ContextAI
Splunk AI Toolkit (CPE: cpe:2.3:a:splunk:splunk_ai_toolkit:*:*:*:*:*:*:*:*) is an add-on for Splunk Enterprise and Splunk Cloud Platform that provides machine learning and AI experiment management, including Experiment Assistants. The vulnerability is classified as CWE-639 (Authorization Bypass Through User-Controlled Key), a subclass of IDOR. When a user queries experiment history, the toolkit accepts caller-supplied parameters that specify the experiment scope - but it does not re-validate that the requested scope belongs to the calling user before executing the history lookup against the backend data store. A 'power' role user (a standard Splunk built-in role granting elevated search and data-management capabilities, below 'admin') can therefore substitute another user's experiment identifiers into these query parameters to read or delete records they are not authorized to access.
RemediationAI
Upgrade Splunk AI Toolkit to version 6.0.0 or later, which resolves the scope-enforcement defect. The vendor patch is confirmed available per Splunk advisory SVD-2026-0808 (https://advisory.splunk.com/advisories/SVD-2026-0808). Where immediate patching is not possible, restrict the 'power' role assignment to the minimum necessary set of users, as this is the prerequisite role for exploitation - reducing the number of 'power'-role accounts directly shrinks the attack surface. Additionally, consider enabling audit logging for experiment history access and deletion events within Splunk AI Toolkit to detect anomalous cross-user access patterns as a detective compensating control. Note that role restriction does not eliminate the vulnerability; it only reduces attacker opportunity until the patch is applied.
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 technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today