Metrics
Affected Vendors & Products
No advisories yet.
Solution
Upgrade Splunk MCP Server to version 1.2.1 or higher.
Workaround
Turn off or remove the Splunk MCP Server app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation.
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-1004 |
|
Wed, 07 Oct 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Splunk MCP Server versions below 1.2.1, Splunk MCP Server could send the Splunk platform authentication token of a user who runs a custom Application Programming Interface (API) tool to the URL configured for that tool. If another user controls that URL, they could capture the token and use it to access data and perform actions as the user who ran the tool. Successful exploitation requires a user who holds a role that contains the mcp_tool_execute capability to run a custom API tool configured by another user. For more information see Configure the Splunk MCP Server (https://help.splunk.com/en/splunk-enterprise/mcp-server-for-splunk-platform/1.2/configure-the-splunk-mcp-server) and Managing custom tools in Splunk MCP Server (https://help.splunk.com/en/splunk-enterprise/mcp-server-for-splunk-platform/1.2/managing-custom-tools-in-splunk-mcp-server) in the Splunk documentation. | |
| Title | Server-Side Request Forgery (SSRF) through Custom API Tools in Splunk MCP Server | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: cisco
Published:
Updated: 2026-10-07T20:46:40.297Z
Reserved: 2026-08-19T12:02:03.622Z
Link: CVE-2026-76286
No data.
Status : Received
Published: 2026-10-07T21:17:20.387
Modified: 2026-10-07T21:17:20.387
Link: CVE-2026-76286
No data.
OpenCVE Enrichment
No data.