obsidian-tc tokens can access arbitrary configured vaults

影響: npm:obsidian-tc < 1.3.1 → 1.3.1

Tool dispatch did not check the caller-supplied input.vault against the caller's bound vault (ctx.vaultId); the folder ACL was a single global instance and the JWT carried no vault claim. As a result, any valid token could read, write, or delete any configured vault by passing input.vault, defeating multi-tenant isolation across ~90 tool sites. (resources/read was the only surface that already guarded this.) Patches Fixed in 1.3.1 (the fix was developed on the v1.3.0 tag, which never published…

Read on GitHub Advisory Database

On 10/24/2026, 02:29 AM, GitHub Advisory Database published "obsidian-tc tokens can access arbitrary configured vaults" (type: Advisory). Severity is "Critical" (critical). Related technologies: JavaScript / Node.js. CVE: CVE-2026-77366.