Skip to main content
VulnerabilityPublished

CVE-2026-20205: Splunk MCP Server · Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.

Affects Splunk MCP ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High : upgrade to 1.0.3 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.3
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade Splunk MCP Server to 1.0.3.

Affected software

ProductAffectedFixed in
SplunkSplunk MCP ServerAffected
  • >=1.0 <1.0.3
Fixed in
  • 1.0.3

AI-suggested

Meanwhile, review and restrict access to the Splunk _internal index and the mcp_tool_admin capability to administrator-level roles only. Follow Splunk's documentation on defining roles and capabilities to minimize exposure. Limit local access to log files to trusted administrators.

Description

In Splunk MCP Server app versions below 1.0.3 , a user who holds a role with access to the Splunk `_internal` index or possesses the high-privilege capability `mcp_tool_admin` could view users session and authorization tokens in clear text.<br><br>The vulnerability would require either local access to the log files or administrative access to internal indexes, which by default only the admin role receives. <br><br>Review roles and capabilities on your instance and restrict internal index access to administrator-level roles. See [Define roles on the Splunk platform with capabilities](https://docs.splunk.com/Documentation/Splunk/latest/Security/Rolesandcapabilities) and [Connecting to MCP Server and Admin settings](https://help.splunk.com/en/splunk-enterprise/mcp-server-for-splunk-platform/connecting-to-mcp-server-and-admin-settings) in the Splunk documentation for more information.

References

Community reviews

Loading reviews…