CVE-2026-77361
4.7MediumPublished 13 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Impact
- High impact on confidentiality
- Weakness
- CWE-59, CWE-863
Impact
A local attacker can read files in restricted vault folders by planting a symlink in an allowed directory. They cannot escape the vault root, but they can bypass folder-level read ACLs.
Root cause
Read ACL checks validate the unresolved lexical path while containment checks evaluate the resolved target path, allowing symlinks to bypass access rules.
Affected systems
obsidian-tc prior to 1.3.1
CVSS v3.1 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Fix & remediation
Upgrade obsidian-tc to version 1.3.1 or later. If patching immediately is not possible, audit the vault and remove any in-vault symlinks pointing to restricted directories.
$ 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, read access-control list (ACL) checks use a lexical vault-relative path while containment checks use the resolved path. An in-vault symlink under an allowed glob that resolves into a denied folder can therefore bypass the read ACL and expose files in the denied folder. Exploitation requires an out-of-band-planted symlink and does not permit an escape from the vault root. Version 1.3.1 fixes the vulnerability by applying ACL checks to the resolved vault-relative path.