Splunk has issued security patches to address 17 vulnerabilities spanning several of its apps and add-ons, among them Splunk MCP Server, the AI Toolkit, and Connect for Kafka. The most serious issue uncovered is a critical remote code execution (RCE) bug in MCP Server, rated CVSS 9.1, which enables attackers with certain privileges to run arbitrary commands on the operating system. This advisory, made public on August 19, 2026, also covers related tools like Cisco Talos Intelligence for Enterprise Security Cloud and Splunk On-Call (VictorOps). ([cybersecuritynews.com](https://cybersecuritynews.com/splunk-patches-security-flaws/))
Details on Key Vulnerabilities
The MCP Server RCE, tracked as CVE-2026-76404, affects versions before 1.2.1. It arises from a flaw in the credential-management module that allows unsafe deserialization, opening the door to command execution when untrusted data is processed. Administrators are instructed to upgrade to version 1.2.1 or remove/disable the app until they can apply the patch. ([cybersecuritynews.com](https://cybersecuritynews.com/splunk-patches-security-flaws/))
The Splunk AI Toolkit was hit with nine unique flaws. Among the most troubling is CVE-2026-76395, which allows a user with “power” role to execute arbitrary code by loading a malicious model containing sparse matrix data. This issue also stems from unsafe deserialization using embedded pickle data. Other high-severity bugs allow privilege escalation, unauthorized container control, tampering with experiment history, and manipulating scheduled searches. The fixes span version 6.0.0 or higher; some fixes are only in version 6.0.1. ([cybersecuritynews.com](https://cybersecuritynews.com/splunk-patches-security-flaws/))
Splunk Connect for Kafka had four vulnerabilities patched in version 2.2.7. These span high risks like credential exposure via HTTP Event Collector (HEC), insecure connector configuration, and potential data interception or DoS attacks. Vulnerabilities included SSRF, flawed certificate validation, and issues specifically tied to HEC in Kerberos setups. ([cybersecuritynews.com](https://cybersecuritynews.com/splunk-patches-security-flaws/))
Other affected components include Cisco Talos Intelligence, where an SSRF exposed tokens; and Splunk On-Call (VictorOps), which had partial exposure of API keys. Fixed versions are 1.0.3 for Talos and 1.0.43 for On-Call. ([cybersecuritynews.com](https://cybersecuritynews.com/splunk-patches-security-flaws/))
What Organizations Should Do
Users should identify which Splunk apps and add-ons are installed in their environments and check whether they are running the affected versions. For MCP Server, an upgrade to at least version 1.2.1 is essential; AI Toolkit users on version 5.7 should move to 6.0.0, while those already on 6.0 need 6.0.1. Kafka Connect deployments should update to version 2.2.7. ([cybersecuritynews.com](https://cybersecuritynews.com/splunk-patches-security-flaws/))
Mitigation steps include disabling or removing affected apps until updates are applied, limiting access to administrative interfaces and REST APIs, enforcing secure transport and certificate validation, and reviewing role assignments to reduce unnecessary privileges. ([cybersecuritynews.com](https://cybersecuritynews.com/splunk-patches-security-flaws/))
Why it matters: The range and severity of these flaws—especially those enabling remote code execution or deserialization attacks—pose dangerous exposure for organizations using Splunk in sensitive or network-facing contexts. Attackers who gain access can exploit low-privileged users, misuse admin interfaces, or poison models to do far greater damage.
