CVE-2026-77366
obsidian-tc tokens can access arbitrary configured vaults
Tool dispatch did not check the caller-supplied input.vault against the caller's bound vault (ctx.vaultId); the folder ACL was a single global instance and the JWT carried no vault claim. As a result, any valid token could read, write, or delete any configured vault by passing input.vault, defeating multi-tenant isolation across ~90 tool sites.
- The-40-Thieves obsidian-tc
- Critical
- CVSS 9.9
- EPSS 0.31%
- Fixed version listed
What to do
Fixed version listed
Affected products
| Product | Affected | Fixed in |
|---|---|---|
| The-40-Thieves obsidian-tc | < 1.3.1 | None listed |
Affected packages
| Package | Affected | Fixed in | Advisory |
|---|---|---|---|
| obsidian-tc (npm) | < 1.3.1 | 1.3.1 | GHSA-84c9-qqpq-2pq5 |
Scores and signals
- Exploitation
- No known exploitation
- Severity
- Critical, CVSS 9.9 (v3.1, scored by GitHub)
- EPSS
- 0.31% chance of exploitation in the next 30 days (EPSS from FIRST, as of Oct 23, 2026)
- CISA's SSVC decision points
- Exploitation: none. Automatable: no. Technical impact: total. As of Oct 13, 2026.
- Weakness
- CWE-639: Authorization Bypass Through User-Controlled Key; CWE-863: Incorrect Authorization
- Vendor
- The-40-Thieves, obsidian-tc
Timeline
- GitHub published advisory GHSA-84c9-qqpq-2pq5 (critical). Fixed in 1.3.1.