CVE-2026-76286: Splunk MCP Server · The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Affects Splunk MCP ServerSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.2.1 when convenient.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.2.1
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade Splunk MCP Server and com.splunk/mcp-server to 1.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk MCP Server | Affected
| Fixed in
|
Mavencom.splunk/mcp-serverpkg:maven/com.splunk/mcp-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Splunk MCP Server version 1.2.1. Users should upgrade to version 1.2.1 or later to remediate this vulnerability. Until upgraded, restrict roles with the mcp_tool_execute capability and carefully control the configuration of custom API tools to trusted URLs only.
Description
CVE-2026-76286 affects Splunk MCP Server versions 1.2 up to but not including 1.2.1. The vulnerability allows a user with the mcp_tool_execute capability to run a custom API tool that sends the user's Splunk platform authentication token to a URL controlled by another user. This could enable the attacker to capture the token and impersonate the original user to access data and perform actions. The issue arises because the server does not sufficiently verify that the URL request is sent to the expected destination.