Live › vulnerability › CVE-2026-77361
Go to dashboardobsidian-tc, an MCP server for Obsidian vaults, checks its read access rules against the vault-relative path but enforces containment on the resolved real path. A symlink inside an allowed folder that points into a denied folder passes the access check.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| obsidian-tc | npm | < 1.3.1 | 1.3.1 |
npm ls obsidian-tc (affected below 1.3.1)
Review the vault for symlinks placed under allowed globs that resolve into denied folders: find <vault> -type l -ls
1.3.1 (npm install obsidian-tc@^1.3.1)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
ACL checks ran on the lexical vault-relative path while containment used the realpath. An in-vault symlink placed under an allowed glob, whose realpath resolved into a denied folder, passed the read ACL — an intra-vault read-ACL-scope bypass. It requires an out-of-band-planted symlink (no MCP tool creates one) and is not a vault-root escape.
Fixed in 1.3.1. Upgrade to >= 1.3.1. ACL enforcement now derives the realpath vault-relative path and feeds a single unified predicate at every site.
Do not permit untrusted symlinks inside the vault.
This page as .md · .json · in your agent: get_signal("CVE-2026-77361")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.