{"answers":{"affected":"2 open source packages ship an affected version, including obsidian-tc.","exploited":"There is no known exploitation of CVE-2026-77362 in the wild and no public exploit code.","fix":"Upgrade obsidian-tc to 1.3.1 or later.","what":"CVE-2026-77362 is a medium-severity missing authorization vulnerability in The-40-Thieves obsidian-tc, published on 13 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-77362 and fix it if it is affected.\n\nWhat it is: CVE-2026-77362 is a medium-severity missing authorization vulnerability in The-40-Thieves obsidian-tc, published on 13 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-77362 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-77362/ (Markdown: https://insights.sbomify.com/CVE-2026-77362/index.md)","id":"CVE-2026-77362","markdown":"https://insights.sbomify.com/CVE-2026-77362/index.md","name":"CVE-2026-77362","record":{"aliases":["GHSA-43r2-c7g8-prc8"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Obsidian MCP server","requires_auth":"low_privilege","summary":"An authenticated attacker can read data from notes outside their permitted access control list via bridge tools in the obsidian-tc server.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, bridge tools do not consistently apply the read access-control list (ACL) to every returned field. The tasks_filter tool exposes group counts derived from denied notes, makemd_query passes unfiltered sibling result fields through, and list_templates exposes template paths and parsed user-function bodies without a read-whitelist check. An authenticated caller can consequently infer or read data from notes outside the caller's read ACL. Version 1.3.1 fixes the vulnerability by filtering path-attributable fields and applying the read whitelist to list_templates.","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 bridge tools expose data outside the read ACL","id":"CVE-2026-77362","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":"obsidian-tc Streamable HTTP transport permits cross-origin loopback vault access","id":"CVE-2026-77363"},"packages":[{"ecosystem":"npm","fixed":["1.3.1"],"introduced":["0"],"last_affected":[],"package":"obsidian-tc","purl":null,"source":"GHSA-43r2-c7g8-prc8"},{"ecosystem":"npm","fixed":["1.3.1"],"introduced":["0"],"last_affected":[],"package":"obsidian-tc","purl":"pkg:npm/obsidian-tc","source":"GHSA-43r2-c7g8-prc8"}],"prev":{"headline":"obsidian-tc symlink path mismatch bypasses read ACL restrictions","id":"CVE-2026-77361"},"products":["obsidian-tc"],"published":"2026-10-13","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":"partial"},"state":"PUBLISHED","updated":"2026-10-13","vendors":["The-40-Thieves"]},"summary":"An authenticated attacker can read data from notes outside their permitted access control list via bridge tools in the obsidian-tc server.","url":"https://insights.sbomify.com/CVE-2026-77362/"}