{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-20205 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-20205 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-20205 is a high-severity vulnerability in Splunk MCP Server, published on 15 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-20205 and fix it if it is affected.\n\nWhat it is: CVE-2026-20205 is a high-severity vulnerability in Splunk MCP Server, published on 15 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-20205 in the wild and no public exploit code.\n\nAffected product: Splunk MCP Server. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-20205/ (Markdown: https://insights.sbomify.com/CVE-2026-20205/index.md)","id":"CVE-2026-20205","markdown":"https://insights.sbomify.com/CVE-2026-20205/index.md","name":"CVE-2026-20205","record":{"aliases":["GHSA-6qfc-m9fp-c5rm"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Splunk MCP Server","requires_auth":"high_privilege","summary":"Privileged users can view session and authorization tokens in clear text within the internal index, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.\u003cbr\u003e\u003cbr\u003eThe vulnerability would require either local access to the log files or administrative access to internal indexes, which by default only the admin role receives. \u003cbr\u003e\u003cbr\u003eReview 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Sensitive Information Disclosure in ''_internal'' index in Splunk MCP Server app","id":"CVE-2026-20205","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Cisco ThousandEyes BrowserBot Command Injection Vulnerability","id":"CVE-2026-20206"},"packages":[],"prev":{"headline":"Improper Handling and Insufficient Isolation of Specific Temporary Files in Splunk Enterprise","id":"CVE-2026-20204"},"products":["Splunk MCP Server"],"published":"2026-04-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-15","vendors":["Splunk"]},"summary":"Privileged users can view session and authorization tokens in clear text within the internal index, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-20205/"}