CVE-2026-77362
4.3MediumPublished 13 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Impact
- Limited impact
- Weakness
- CWE-200, CWE-863
Impact
Authenticated callers can read note contents, template paths, function bodies, and task metadata outside their authorized read ACL. Exploitation requires network access and a valid low-privileged account.
Root cause
Bridge tools fail to consistently apply read ACLs and whitelist checks across all returned fields and query results.
Affected systems
obsidian-tc prior to 1.3.1
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Fix & remediation
Upgrade obsidian-tc to version 1.3.1. No interim mitigation is provided.
$ npm install obsidian-tc@1.3.1AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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 tasks_filter tool exposes group counts derived from denied notes, makemd_query passes unfiltered sibling result fields through, and list_templates 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 list_templates.