CVE-2026-76398

Splunk AI Toolkit versions below 6.0.1 are affected by an improper access control vulnerability in the REST API. A user without the "admin" or "power" Splunk role can delete the experiment history of another user without authorization. The root cause is that the toolkit deletes experiment history...

CVE-2026-76397

Splunk AI Toolkit versions below 6.0.0 are affected: a user with the "power" Splunk role can access and delete all experiment history data, including other users' data, because the tool does not preserve the trusted experiment scope when processing caller-controlled query values. CVSS 8.1 (HIGH) ...

CVE-2026-76397 Improper Access Control in Experiment History through the REST API in Splunk AI Toolkit

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...

CVE-2026-76396

Splunk AI Toolkit versions below 6.0.0 fail to mark the apply search command as risky, allowing users with the schedule_search capability to trigger deserialization of arbitrary model files via scheduled searches. This can lead to code execution with high confidentiality, integrity, and availabil...

CVE-2026-76396 Improper Access Control through Scheduled Searches in Splunk AI Toolkit

In Splunk AI Toolkit versions below 6.0.0, a user that holds a role with the schedulesearch capability could cause a scheduled search to load and deserialize a model file through the apply search command. The improper access control is possible because Splunk AI Toolkit does not mark the apply...

CVE-2026-76395

Splunk AI Toolkit versions below 6.0.0 deserialize sparse matrix data containing embedded pickle payloads without validation, allowing a user with the "power" role to execute arbitrary code via the model-loading REST API. The fix is to upgrade to version 6.0.0 or later. No in-the-wild exploitatio...

CVE-2026-76394

Splunk AI Toolkit versions below 6.0.0 have multiple REST API handlers that fail to enforce authorization checks, allowing low-privileged users (without admin or power roles) to start/stop/configure containers and read/modify connection and configuration data. CVSS 8.3 HIGH; remediation is to upg...

CVE-2026-76393

CVE-2026-76393 is a race condition in Splunk AI Toolkit versions below 6.0.0 , occurring during model upload through the REST API . The root cause is that the toolkit does not verify that the uploaded content belongs to the request that creates the model lookup entry. An authenticated user who ca...

CVE-2026-76392

Splunk AI Toolkit versions below 6.0.0 contain a hard-coded credential vulnerability in its container service connections. The toolkit generates or stores credentials for connected container services using predictable or hard-coded default values , allowing a user who does not hold the "admin" or...

CVE-2026-76391

In Splunk AI Toolkit versions below 6.0.0, the Agent Run History handler swaps the caller's session key for a system token, allowing low-privilege users to run system-level searches, access all data, and read or delete other users' search jobs. CVSS 3.1 scores 8.3 (HIGH). No exploitation evidence...

PT-2026-78823

Name of the Vulnerable Software and Affected Versions Splunk AI Toolkit versions prior to 6.0.0 Description Improper access control allows a user with the schedule search capability to cause a scheduled search to load and deserialize a model file. This occurs because the apply search command is n...

PT-2026-78822

Name of the Vulnerable Software and Affected Versions Splunk AI Toolkit versions prior to 6.0.0 Description A user with the "power" Splunk role can execute arbitrary code on the Splunk server by loading a model file containing crafted sparse matrix data. This occurs because a model codec...

PT-2026-78824

Name of the Vulnerable Software and Affected Versions Splunk AI Toolkit versions prior to 6.0.0 Description A user with the "power" Splunk role can access and delete experiment history data belonging to other users. This occurs because the application fails to preserve the trusted experiment scop...

PT-2026-78820

Name of the Vulnerable Software and Affected Versions Splunk AI Toolkit versions prior to 6.0.0 Description A race condition exists when users upload models. An attacker with upload permissions can overwrite a model being uploaded by another user by sending a concurrent upload request using the...

PT-2026-78821

Name of the Vulnerable Software and Affected Versions Splunk AI Toolkit versions prior to 6.0.0 Description Low-privileged users without admin or power roles can start, stop, and configure containers, as well as read or modify connection and configuration data. This occurs because multiple handle...

PT-2026-78819

🚨 CVE-2026-76392 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...

CVE-2026-20265

In Splunk AI Toolkit versions below 5.7.4, a low-privileged user that does not hold the "admin" or "power" Splunk roles could cause the Splunk AI Toolkit to make outbound requests over HTTP to a server that an attacker controls, which could allow for data exfiltration. The vulnerability exists...

CVE-2026-20266

Summary: CVE-2026-20266 affects Splunk AI Toolkit

CVE-2026-20266 OS Command Injection in the btool Configuration Helper in Splunk AI Toolkit

In Splunk AI Toolkit versions below 5.7.4, a user who holds the "admin" Splunk role could execute arbitrary OS commands on the host running the Splunk Enterprise instance. The vulnerability is possible because of an unsafe shell execution pattern in the btool configuration helper, which construct...

CVE-2026-20265

Splunk AI Toolkit has a vulnerability in versions below 5.7.4 where a low-privilege user (not admin/power) can cause the toolkit to issue outbound HTTP requests to an attacker-controlled server due to an insecure default domain allowlist. This could enable data exfiltration. Root cause: outbound ...