Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.9

Obsidian‑TC tokens can access any vault

CVE-2026-77366 · published 6 days ago
Summary

In versions before 1.3.1, the digital key used to talk to Obsidian‑TC did not lock you to a specific vault, so anyone with a valid key could choose a different vault and read, change, or delete its files. The problem is fixed in version 1.3.1, which ties each key to a single vault and blocks mismatched requests. Upgrade to version 1.3.1 or later as soon as possible.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
the-40-thieves obsidian-tc < 1.3.1
Original advisory text
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.
References
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
9.9 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-639Authorization Bypass Through User-Controlled Key
CWE-863Incorrect Authorization
Timeline
Published12 Oct 2026
Updated16 Oct 2026
First seen12 Oct 2026
Sources
CVE-2026-77366 · NVD
CVE-2026-77366 · MITRE
CVE-2026-77366 · OSV
GHSA-84c9-qqpq-2pq5 · GHSA
Track software like this
Free during beta