CVE-2026-77364 obsidian-tc fail-open default ACL exposes Obsidian control-directory secrets
An authenticated attacker can read sensitive control directory files, exposing secrets like API keys and passwords, due to fail-open default ACLs.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-77364?
CVE-2026-77364 is a medium-severity missing authorization vulnerability in The-40-Thieves obsidian-tc, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, undefined readPaths and writePaths settings allow all paths, strictReadDefault does not protect direct requests, and the .obsidian, .git, and .trash control directories are excluded only during enumeration. An authenticated caller can directly read sensitive files such as .obsidian/plugins/*/data.json, potentially exposing plugin API keys, Obsidian Sync passwords, and other in-vault data. Version 1.3.1 fixes the vulnerability by denying the control directories by default and enforcing strictReadDefault on direct request paths.
Which versions are affected by CVE-2026-77364?
2 open source packages ship an affected version, including obsidian-tc.
| Package | Affected | Fixed in |
|---|---|---|
obsidian-tc npm | All versions | 1.3.1 |
obsidian-tc npm | All versions | 1.3.1 |
How do I fix CVE-2026-77364?
Upgrade obsidian-tc to 1.3.1 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-77364 being exploited?
There is no known exploitation of CVE-2026-77364 in the wild and no public exploit code.
Sources
Also known as GHSA-cvp8-vvgf-69q4.