EUVD-2026-62969
GHSA-3v49-2fcm-3rcj
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Requires the Splunk admin role (PR:H) over the network with low complexity; deserialization yields OS command execution that escapes the app into the host, so S:C and C/I/A all High.
Primary rating from Vendor (cisco).
CVSS VectorVendor: cisco
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Operating-system command execution in the Splunk MCP Server app (all versions below 1.2.1) lets a user already holding the Splunk 'admin' role run arbitrary commands on the underlying host by abusing unsafe deserialization in the credential-management component. Because the app trusts stored data and deserializes it without verifying the object type, a privileged Splunk user can escalate from application-level administration to full host compromise. No public exploit identified at time of analysis, and it is not listed in CISA KEV; a vendor patch is available.
Technical ContextAI
The affected component is the Splunk MCP Server app (cpe:2.3:a:splunk:splunk_mcp_server_app), an add-on that exposes Model Context Protocol server functionality within a Splunk deployment. The root cause is CWE-502 (Deserialization of Untrusted Data): the credential-management code reads previously stored credential data and reconstructs (deserializes) it into live objects without validating that the serialized content matches the expected type. In languages/serialization formats that support object instantiation during deserialization, a crafted stored payload can trigger execution of attacker-controlled code paths ('gadget chains') at deserialization time, converting stored data into OS command execution on the Splunk host.
RemediationAI
Vendor-released patch: upgrade the Splunk MCP Server app to version 1.2.1 or later, per Splunk advisory SVD-2026-0808 (https://advisory.splunk.com/advisories/SVD-2026-0808). If immediate patching is not possible, reduce risk by tightly restricting who holds the Splunk 'admin' role and auditing current admin-role assignments, since exploitation requires that role - the trade-off is reduced administrative flexibility for other legitimate admins. As an additional compensating control, consider temporarily disabling or uninstalling the MCP Server app if it is not in active use (trade-off: loss of MCP functionality), and monitor the Splunk host for unexpected child processes spawned by the Splunk service account to detect command-execution attempts. Enforce strong authentication/MFA and session controls on Splunk admin accounts to limit account takeover, which is the main path to reaching PR:H.
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-502 – Deserialization of Untrusted Data
View allSame technique Deserialization
View allShare
External POC / Exploit Code
Leaving vuln.today