{"answers":{"affected":"2 open source packages ship an affected version, including obsidian-tc.","exploited":"There is no known exploitation of CVE-2026-77366 in the wild and no public exploit code.","fix":"Upgrade obsidian-tc to 1.3.1 or later.","what":"CVE-2026-77366 is a critical missing authorization vulnerability in The-40-Thieves obsidian-tc, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77366 and fix it if it is affected.\n\nWhat it is: CVE-2026-77366 is a critical missing authorization vulnerability in The-40-Thieves obsidian-tc, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-77366 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-77366/ (Markdown: https://insights.sbomify.com/CVE-2026-77366/index.md)","id":"CVE-2026-77366","markdown":"https://insights.sbomify.com/CVE-2026-77366/index.md","name":"CVE-2026-77366","record":{"aliases":["GHSA-84c9-qqpq-2pq5"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Obsidian MCP server","requires_auth":"low_privilege","summary":"Attackers with valid tokens can access arbitrary Obsidian vaults to read, write, or delete data due to missing vault binding checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, tool dispatch does not compare the caller-controlled input.vault value with the vault bound to the caller, the JSON Web Token (JWT) has no vault claim, and the folder access-control list is shared globally. Any valid token can therefore select another configured vault and read, write, or delete its contents through affected tools. Version 1.3.1 fixes the vulnerability by binding tokens and request context to a vault and rejecting mismatched input.vault values before scope checks.","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 tokens can access arbitrary configured vaults","id":"CVE-2026-77366","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"SeaweedFS: Authenticated Cross-Prefix IDOR in Filer TUS Handler Enables Arbitrary Write to Tenant-Forbidden Paths","id":"CVE-2026-77368"},"packages":[{"ecosystem":"npm","fixed":["1.3.1"],"introduced":["0"],"last_affected":[],"package":"obsidian-tc","purl":null,"source":"GHSA-84c9-qqpq-2pq5"},{"ecosystem":"npm","fixed":["1.3.1"],"introduced":["0"],"last_affected":[],"package":"obsidian-tc","purl":"pkg:npm/obsidian-tc","source":"GHSA-84c9-qqpq-2pq5"}],"prev":{"headline":"Optimole \u003c= 4.2.10 - Unauthenticated Stored Cross-Site Scripting via 'a' (above_fold_images) Parameter","id":"CVE-2026-77365"},"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":"Attackers with valid tokens can access arbitrary Obsidian vaults to read, write, or delete data due to missing vault binding checks.","url":"https://insights.sbomify.com/CVE-2026-77366/"}