{"answers":{"affected":"2 open source packages ship an affected version, including obsidian-tc.","exploited":"There is no known exploitation of CVE-2026-77364 in the wild and no public exploit code.","fix":"Upgrade obsidian-tc to 1.3.1 or later.","what":"CVE-2026-77364 is a medium-severity 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-77364 and fix it if it is affected.\n\nWhat it is: CVE-2026-77364 is a medium-severity 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-77364 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-77364/ (Markdown: https://insights.sbomify.com/CVE-2026-77364/index.md)","id":"CVE-2026-77364","markdown":"https://insights.sbomify.com/CVE-2026-77364/index.md","name":"CVE-2026-77364","record":{"aliases":["GHSA-cvp8-vvgf-69q4"],"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 sensitive control directory files, exposing secrets like API keys and passwords, due to fail-open default ACLs.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"},{"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, undefined readPaths and writePaths settings allow all paths, strictReadDefault does not protect direct requests, and the .obsidian, .git, and .trash control directories are excluded only during enumeration. An authenticated caller can directly read sensitive files such as .obsidian/plugins/*/data.json, potentially exposing plugin API keys, Obsidian Sync passwords, and other in-vault data. Version 1.3.1 fixes the vulnerability by denying the control directories by default and enforcing strictReadDefault on direct request paths.","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 fail-open default ACL exposes Obsidian control-directory secrets","id":"CVE-2026-77364","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":"Optimole \u003c= 4.2.10 - Unauthenticated Stored Cross-Site Scripting via 'a' (above_fold_images) Parameter","id":"CVE-2026-77365"},"packages":[{"ecosystem":"npm","fixed":["1.3.1"],"introduced":["0"],"last_affected":[],"package":"obsidian-tc","purl":null,"source":"GHSA-cvp8-vvgf-69q4"},{"ecosystem":"npm","fixed":["1.3.1"],"introduced":["0"],"last_affected":[],"package":"obsidian-tc","purl":"pkg:npm/obsidian-tc","source":"GHSA-cvp8-vvgf-69q4"}],"prev":{"headline":"obsidian-tc Streamable HTTP transport permits cross-origin loopback vault access","id":"CVE-2026-77363"},"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":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["The-40-Thieves"]},"summary":"An authenticated attacker can read sensitive control directory files, exposing secrets like API keys and passwords, due to fail-open default ACLs.","url":"https://insights.sbomify.com/CVE-2026-77364/"}