The-40-Thieves obsidian-tc
obsidian-tc tokens can access arbitrary configured vaults
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, tool dispatch does not compare the caller-controlled input.vault value with the vault bound to the caller, the JSON Web Token (JWT) has no vault claim, and the folder access-control list is shared globally. Any valid token can therefore select another configured vault and read, write, or delete its contents through affected tools. Version 1.3.1 fixes the vulnerability by binding tokens and request context to a vault and rejecting mismatched input.vault values before scope checks.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.3.1
Fixed in 1.3.1
Mitigation
Upgrade obsidian-tc to 1.3.1 or later.
References
- Vendor advisory github.com/The-40-Thieves/obsidian-tc/security…
- Patch github.com/The-40-Thieves/obsidian-tc/pull/72
- Patch github.com/The-40-Thieves/obsidian-tc/commit/3…
1 more
- Release notes github.com/The-40-Thieves/obsidian-tc/releases…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.