{"answers":{"affected":"2 open source packages ship an affected version, including obsidian-tc.","exploited":"There is no known exploitation of CVE-2026-77363 in the wild and no public exploit code.","fix":"Upgrade obsidian-tc to 1.3.1 or later.","what":"CVE-2026-77363 is a high-severity server-side request forgery vulnerability in The-40-Thieves obsidian-tc, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-77363 and fix it if it is affected.\n\nWhat it is: CVE-2026-77363 is a high-severity server-side request forgery vulnerability in The-40-Thieves obsidian-tc, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-77363 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- obsidian-tc (npm): affected all versions; fixed in 1.3.1\n- obsidian-tc (npm): affected all versions; fixed in 1.3.1\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-77363/ (Markdown: https://insights.sbomify.com/CVE-2026-77363/index.md)","id":"CVE-2026-77363","markdown":"https://insights.sbomify.com/CVE-2026-77363/index.md","name":"CVE-2026-77363","record":{"aliases":["GHSA-pqh8-4pj7-32xx"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Obsidian MCP server","requires_auth":"none","summary":"A malicious web page can access local Obsidian vaults via the MCP server's HTTP transport when authentication is disabled, bypassing origin checks.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"},{"id":"CWE-1385","name":"Missing Origin Validation in WebSockets"}],"description":"obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, the Streamable HTTP transport does not validate the Host or Origin header or enable DNS-rebinding protection. When the documented loopback configuration uses auth.mode set to none, a malicious web page can send requests to the local MCP endpoint and receive unrestricted vault access through the http-local caller. Version 1.3.1 fixes the vulnerability by enabling host, origin, and DNS-rebinding validation.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"obsidian-tc Streamable HTTP transport permits cross-origin loopback vault access","id":"CVE-2026-77363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"obsidian-tc fail-open default ACL exposes Obsidian control-directory secrets","id":"CVE-2026-77364"},"packages":[{"ecosystem":"npm","fixed":["1.3.1"],"introduced":["0"],"last_affected":[],"package":"obsidian-tc","purl":null,"source":"GHSA-pqh8-4pj7-32xx"},{"ecosystem":"npm","fixed":["1.3.1"],"introduced":["0"],"last_affected":[],"package":"obsidian-tc","purl":"pkg:npm/obsidian-tc","source":"GHSA-pqh8-4pj7-32xx"}],"prev":{"headline":"obsidian-tc bridge tools expose data outside the read ACL","id":"CVE-2026-77362"},"products":["obsidian-tc"],"published":"2026-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-10-13","vendors":["The-40-Thieves"]},"summary":"A malicious web page can access local Obsidian vaults via the MCP server's HTTP transport when authentication is disabled, bypassing origin checks.","url":"https://insights.sbomify.com/CVE-2026-77363/"}