obsidian-tc tokens can access arbitrary configured vaults

Why it is Amber

• CVSS 9.9 critical
• On your watchlist: npm

Affected packages

References

• https://github.com/advisories/GHSA-84c9-qqpq-2pq5
• https://github.com/The-40-Thieves/obsidian-tc/security/advisories/GHSA-84c9-qqpq-2pq5
• https://github.com/The-40-Thieves/obsidian-tc/pull/72
• https://github.com/The-40-Thieves/obsidian-tc/commit/38b4992e87dc2715564236e1a42d005ab05a0194
• https://github.com/The-40-Thieves/obsidian-tc/releases/tag/v1.3.1
• https://nvd.nist.gov/vuln/detail/cve-2026-77366
• https://github.com/advisories/GHSA-84c9-qqpq-2pq5

Original 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.