CVE-2026-77366: obsidian-tc tokens can access arbitrary configured vaults
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.)
References
- github.com/The-40-Thieves/obsidian-tc/commit/38b4992e87dc2715564236e1a42d005ab05a0194
- github.com/The-40-Thieves/obsidian-tc/pull/72
- github.com/The-40-Thieves/obsidian-tc/releases/tag/v1.3.1
- github.com/The-40-Thieves/obsidian-tc/security/advisories/GHSA-84c9-qqpq-2pq5
- github.com/advisories/GHSA-84c9-qqpq-2pq5
- nvd.nist.gov/vuln/detail/CVE-2026-77366
- nvd.nist.gov/vuln/detail/cve-2026-77366
Code Behaviors & Features
Detect and mitigate CVE-2026-77366 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →