CVE-2026-77362: obsidian-tc bridge tools expose data outside the read ACL
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 tasksfilter tool exposes group counts derived from denied notes, makemdquery passes unfiltered sibling result fields through, and listtemplates 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 listtemplates.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
obsidian-tcto a version that resolves this vulnerability.Fixed in 1.3.1
Event History
Frequently Asked Questions
Which callers are exposed to this issue?
Authenticated callers with access to the MCP server are exposed if their permissions restrict access to some vault notes. They may infer or read information from notes that fall outside their assigned read ACL.
Which bridge tools can leak restricted information?
tasks_filter can expose group counts derived from denied notes, makemd_query can return unfiltered sibling result fields, and list_templates can expose template paths and parsed user-function bodies without a read-whitelist check.
Are deployments running version 1.3.1 affected?
No. Version 1.3.1 fixes the issue by filtering path-attributable fields and applying the read whitelist to list_templates.