File disclosure via lexical-path symlink ACL bypass
Published Oct 13, 2026 · Updated Oct 13, 2026
Read-ACL bypass in The-40-Thieves obsidian-tc before 1.3.1 allows local users to read denied vault files via an allowed-path symlink. Read authorization checks the lexical vault-relative path while containment checks the resolved path, so a link under an allowed glob passes authorization even when its target is in a denied folder. Exploitation requires an out-of-band-planted symlink that no MCP tool creates; disclosure remains inside the vault root.
Summary
What happened
Read-ACL bypass in The-40-Thieves obsidian-tc before 1.3.1 allows local users to read denied vault files via an allowed-path symlink. Read authorization checks the lexical vault-relative path while containment checks the resolved path, so a link under an allowed glob passes authorization even when its target is in a denied folder. Exploitation requires an out-of-band-planted symlink that no MCP tool creates; disclosure remains inside the vault root.
The record
- CVE
- CVE-2026-77361
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Vendor
- The-40-Thieves
- Product
- obsidian-tc
- Classifications
- CWE-863, CWE-59, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 13, 2026CVE publishedPublication date reported by the CVE source.
- Oct 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started