{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76286 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76286 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76286 is a medium-severity server-side request forgery vulnerability in Splunk MCP Server, published on 7 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-76286 and fix it if it is affected.\n\nWhat it is: CVE-2026-76286 is a medium-severity server-side request forgery vulnerability in Splunk MCP Server, published on 7 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-76286 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-76286/ (Markdown: https://insights.sbomify.com/CVE-2026-76286/index.md)","id":"CVE-2026-76286","markdown":"https://insights.sbomify.com/CVE-2026-76286/index.md","name":"CVE-2026-76286","record":{"aliases":["GHSA-mgwr-9j5x-6w4x"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Splunk MCP Server","requires_auth":"high_privilege","summary":"Attackers can capture authentication tokens via SSRF in custom API tools, allowing unauthorized data access and actions as the victim user.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","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":"Server-Side Request Forgery (SSRF) through Custom API Tools in Splunk MCP Server","id":"CVE-2026-76286","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Authorization Bypass in the Data Management REST API in Splunk Enterprise","id":"CVE-2026-76287"},"packages":[],"prev":{"headline":"Improper Adherence to Coding Standards in Splunk Enterprise","id":"CVE-2026-76285"},"products":["Splunk MCP Server"],"published":"2026-10-07","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":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["Splunk"]},"summary":"Attackers can capture authentication tokens via SSRF in custom API tools, allowing unauthorized data access and actions as the victim user.","url":"https://insights.sbomify.com/CVE-2026-76286/"}