Security Hardening Release for Splunk Apps and Add-ons - August 2026

CVE-2026-76389: Server-Side Request Forgery (SSRF) through the REST API in Cisco Talos Intelligence for Enterprise Security Cloud

Description

In Cisco Talos Intelligence for Enterprise Security Cloud versions below 1.0.3, a user that holds a role with the get_talos_enrichment capability could send a crafted request to the Talos intelligence enrichment Representational State Transfer (REST) API endpoint and cause the instance to make an outbound request to an attacker-controlled server. The request could expose tokens that compromise all relevant data and system integrity in the Splunk instance. The vulnerability is possible because the Talos intelligence enrichment REST endpoint accepts the destination for authenticated Splunk management requests from request data. For more information see Deploy Cisco Talos Intelligence for Splunk Enterprise Security in the Splunk documentation.

Bug ID: VULN-74170

CWE: CWE-918

CVSSv3.1 Score: 8.8, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Mitigations and Workarounds

Turn off or remove the Cisco Talos Intelligence for Enterprise Security Cloud app. For more information see Manage app and add-on objects in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76390: Information Disclosure through Splunk Web in Cisco Talos Intelligence for Enterprise Security Cloud

Description

In Cisco Talos Intelligence for Enterprise Security Cloud versions below 1.0.3, an unauthenticated user could access the add-on OpenAPI specification through Splunk Web static file paths. The exposed specification could allow for reconnaissance of the add-on Representational State Transfer (REST) API endpoints and authentication model. The vulnerability is possible because the generated OpenAPI specification is packaged in a static file path that Splunk Web serves without authentication. For more information see Deploy Cisco Talos Intelligence for Splunk Enterprise Security in the Splunk documentation.

Bug ID: VULN-74171

CWE: CWE-200

CVSSv3.1 Score: 5.3, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Mitigations and Workarounds

Turn off or remove the Cisco Talos Intelligence for Enterprise Security Cloud app. For more information see Manage app and add-on objects in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76391: Improper Privilege Management through Agent Run History in Splunk AI Toolkit

Description

In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the “admin” or “power” Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad in the Splunk documentation.

Bug ID: VULN-73540

CWE: CWE-863

CVSSv3.1 Score: 8.3, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Mitigations and Workarounds

Turn off or remove the Splunk AI Toolkit app. For more information see 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 and DSDL install/version dependencies in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76392: Use of Hard-coded Credentials in Container Connections in Splunk AI Toolkit

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 in the Splunk documentation.

Bug ID: VULN-68567

CWE: CWE-798

CVSSv3.1 Score: 5.4, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Mitigations and Workarounds

Turn off or remove the Splunk AI Toolkit app. For more information see 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 and DSDL install/version dependencies in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76393: Race Condition during Model Upload through the REST API in Splunk AI Toolkit

Description

In Splunk AI Toolkit versions below 6.0.0, a user who can upload models could overwrite a model being uploaded by another user by sending a concurrent upload request for the same model name, causing the resulting model lookup entry to reference attacker-controlled content. The race condition is possible because Splunk AI Toolkit does not verify that the uploaded content belongs to the request that creates the model lookup entry. For more information see Troubleshoot the Splunk Machine Learning Toolkit in the Splunk documentation.

Bug ID: VULN-80342

CWE: CWE-362

CVSSv3.1 Score: 5.9, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L

Mitigations and Workarounds

Turn off or remove the Splunk AI Toolkit app. For more information see 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 and DSDL install/version dependencies in the Splunk documentation.

Acknowledgments: Shimamine Taihei (島峰 泰平)

CVE-2026-76394: Missing Authorization in Container and Connection Management through the REST API in Splunk AI Toolkit

Description

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 in the Splunk documentation.

Bug ID: VULN-73539

CWE: CWE-862

CVSSv3.1 Score: 8.3, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Mitigations and Workarounds

Turn off or remove the Splunk AI Toolkit app. For more information see 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 and DSDL install/version dependencies in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76395: Remote Code Execution (RCE) through Deserialization of Untrusted Data in the Model Loading REST API in Splunk AI Toolkit

Description

In Splunk AI Toolkit versions below 6.0.0, a user who holds the “power” Splunk role could execute arbitrary code on the Splunk server by loading a model file containing crafted sparse matrix data. The deserialization of untrusted data is possible because a model codec in Splunk AI Toolkit deserializes sparse matrix data without guarding against embedded pickle content. For more information see Troubleshoot the Splunk Machine Learning Toolkit in the Splunk documentation.

Bug ID: VULN-72150

CWE: CWE-502

CVSSv3.1 Score: 8.8, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Mitigations and Workarounds

Turn off or remove the Splunk AI Toolkit app. For more information see 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 and DSDL install/version dependencies in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk

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

Description

In Splunk AI Toolkit versions below 6.0.0, a user that holds a role with the schedule_search 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 search command as risky. For more information see Troubleshoot the AI Toolkit in the Splunk documentation.

Bug ID: VULN-73542

CWE: CWE-269

CVSSv3.1 Score: 7.5, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Mitigations and Workarounds

Turn off or remove the Splunk AI Toolkit app. For more information see 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 and DSDL install/version dependencies in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk

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

Description

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 in the Splunk documentation.

Bug ID: VULN-91795

CWE: CWE-639

CVSSv3.1 Score: 8.1, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Mitigations and Workarounds

Turn off or remove the Splunk AI Toolkit app. For more information see Manage app and add-on objects in the Splunk documentation.

CVE-2026-76398: Improper Access Control during Experiment History Deletion through the REST API in Splunk AI Toolkit

Description

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 in the Splunk documentation.

Bug ID: VULN-91787

CWE: CWE-862

CVSSv3.1 Score: 4.3, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Mitigations and Workarounds

Turn off or remove the Splunk AI Toolkit app. For more information see Manage app and add-on objects in the Splunk documentation.

CVE-2026-76399: Incorrect Permission Assignment for Scheduled Searches in Splunk AI Toolkit

Description

In Splunk AI Toolkit versions below 6.0.1, a user who holds the “power” Splunk role could modify app-provided scheduled searches to run arbitrary Search Processing Language (SPL) using the permissions of the search owner, which could allow access to all relevant data and affect system integrity. The vulnerability is possible because Splunk AI Toolkit gives the “power” Splunk role permission to modify scheduled searches that run using the permissions of the search owner.

Bug ID: VULN-91316

CWE: CWE-732

CVSSv3.1 Score: 8.1, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Mitigations and Workarounds

Turn off or remove the Splunk AI Toolkit app. For more information see Manage app and add-on objects in the Splunk documentation.

CVE-2026-76400: Denial of Service (DoS) through the REST API in Splunk Connect for Kafka

Description

In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Representational State Transfer (REST) API and influence responses from a Hypertext Transfer Protocol (HTTP) Event Collector endpoint in Splunk Enterprise could cause the connector to retry failed event batches until event delivery stops. The vulnerability is possible because HTTP Event Collector delivery retry handling uses an unbounded default for failed batches instead of a finite retry limit. For more information see Install Splunk Connect for Kafka, Data ingestion parameters for Splunk Connect for Kafka, and Set up and use HTTP Event Collector with configuration files in the Splunk documentation.

Bug ID: VULN-83425

CWE: CWE-400

CVSSv3.1 Score: 5.9, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Mitigations and Workarounds

Restrict access to the Kafka Connect Representational State Transfer (REST) API to trusted administrative hosts and networks. Set a finite HTTP Event Collector retry limit in the connector configuration. For more information see Data ingestion parameters for Splunk Connect for Kafka in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76401: Regular Expression Denial of Service (DoS) through the REST API in Splunk Connect for Kafka

Description

In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Representational State Transfer (REST) API could configure timestamp extraction with a crafted regular expression and matching event data to block a Kafka Connect worker thread, stopping event delivery for the affected connector. The vulnerability is possible because timestamp extraction evaluates customer-supplied regular expressions without a time limit. For more information see Install Splunk Connect for Kafka and Data ingestion parameters for Splunk Connect for Kafka in the Splunk documentation.

Bug ID: VULN-83424

CWE: CWE-407

CVSSv3.1 Score: 5.9, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Mitigations and Workarounds

Restrict access to the Kafka Connect Representational State Transfer (REST) API to trusted administrative hosts and networks. Turn off timestamp extraction by setting enable.timestamp.extraction to false in the connector configuration if you do not use timestamp extraction functionality. For more information see Data ingestion parameters for Splunk Connect for Kafka in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76402: Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for Kafka

Description

In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Representational State Transfer (REST) API could configure a non-secure Hypertext Transfer Protocol (HTTP) Event Collector endpoint in Splunk Enterprise that causes the connector to send authentication credentials to an attacker-controlled server, allowing for exposure of credentials that compromise all relevant data sent through the connector and limited alteration of event delivery. The vulnerability is possible because HTTP Event Collector endpoint validation does not require secure transport by default. For more information see Install Splunk Connect for Kafka, Data ingestion parameters for Splunk Connect for Kafka, and Set up and use HTTP Event Collector with configuration files in the Splunk documentation.

Bug ID: VULN-83423

CWE: CWE-918

CVSSv3.1 Score: 8.2, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigations and Workarounds

Restrict access to the Kafka Connect Representational State Transfer (REST) API to trusted administrative hosts and networks. Keep secure endpoint enforcement turned on so connector configuration requires secure transport for HTTP Event Collector endpoints. If you do not require a secure HTTP Event Collector transport, restrict that traffic to a trusted private network in addition to restricting Kafka Connect REST API access. For more information see Data ingestion parameters for Splunk Connect for Kafka and Set up and use HTTP Event Collector with configuration files in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk

CVE-2026-76403: Improper Certificate Validation through HTTP Event Collector Kerberos Authentication in Splunk Connect for Kafka

Description

In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user positioned in the network path could read or alter all relevant data sent from the connector when Kerberos authentication is used with Hypertext Transfer Protocol (HTTP) Event Collector in Splunk Enterprise. The vulnerability is possible because the Kerberos authentication path does not apply the configured certificate validation options when it builds the HTTP client. For more information see Install Splunk Connect for Kafka, Security configurations for Splunk Connect for Kafka, and Set up and use HTTP Event Collector with configuration files in the Splunk documentation.

Bug ID: VULN-83421

CWE: CWE-295

CVSSv3.1 Score: 7.4, High

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigations and Workarounds

Turn off or remove Splunk Connect for Kafka.

Acknowledgments: Pavan Saxena (RootkId)

CVE-2026-76404: Remote Code Execution (RCE) through Deserialization of Untrusted Data in Splunk MCP Server app

Description

In Splunk MCP Server app versions below 1.2.1, a user who holds the “admin” Splunk role could execute arbitrary commands on the underlying operating system. The vulnerability is possible because of missing input validation in the app’s credential management component, which deserializes stored data without checking whether the content is of the expected type.

Bug ID: VULN-84459

CWE: CWE-502

CVSSv3.1 Score: 9.1, Critical

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Mitigations and Workarounds

Turn off or remove the Splunk MCP Server app. For more information see Manage app and add-on objects in the Splunk documentation.

Acknowledgments: Kuniyoshi Noguchi (KuniNogu)

CVE-2026-76405: Information Disclosure through Cleartext Storage in the App Key Value Store in the Splunk On-Call (VictorOps) app

Description

In Splunk On-Call (VictorOps) app versions below 1.0.43 on Splunkbase, a user who does not hold the “admin” or “power” Splunk roles could read a partially masked Application Programming Interface (API) key from the App Key Value Store (KV Store). The exposure is possible because the Splunk On-Call (VictorOps) app does not fully mask the API key before storing it in a KV Store collection that the user can read. For more information see About the app key value store in the Splunk documentation.

Bug ID: VULN-89261

CWE: CWE-312

CVSSv3.1 Score: 4.3, Medium

CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Mitigations and Workarounds

Turn off or remove the Splunk On-Call (VictorOps) app. For more information see Manage app and add-on objects in the Splunk documentation.

Acknowledgments: Gabriel Nitu, Splunk