obsidian-tc tokens can access arbitrary configured vaults
### Impact 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. (`resources/read` was the only surface that already guarded this.) ### Patches Fixed in **1.3.1** (the fix was developed on the `v1.3.0` tag, which never published to npm; 1.3.1 is the first published release with the fix). Upgrade to `>= 1.3.1`. ### Workarounds Run a single vault per server process, or isolate each tenant on a separate process/credential. ### Fix A central `input.vault === ctx.vaultId` guard was added in dispatch before the scope check.
- Products
- obsidian-tc
- Affected versions
- Not specified
- Fixed versions
- 1.3.1
- CVEs
- CVE-2026-77366
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 22:25 UTC · Revision 1
Source evidence
obsidian-tc tokens can access arbitrary configured vaults
core-osv · Original sourcePublished 23 Oct 2026, 17:29 UTC
### Impact 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. (`resources/read` was the only surface that already guarded this.) ### Patches Fixed in **1.3.1** (the fix was developed on the `v1.3.0` tag, which never published to npm; 1.3.1 is the first published release with the fix). Upgrade to `>= 1.3.1`. ### Workarounds Run a single vault per server process, or isolate each tenant on a separate process/credential. ### Fix A central `input.vault === ctx.vaultId` guard was added in dispatch before the scope check.
osv:GHSA-84c9-qqpq-2pq5
obsidian-tc
Fixed versions: 1.3.1
Complete source record
{
"id": "46e2b60c5ef5948704c4e7906b6a36496d80baed7a9fb3c937a0dcc931478aa3",
"url": "https://osv.dev/vulnerability/GHSA-84c9-qqpq-2pq5",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "obsidian-tc tokens can access arbitrary configured vaults",
"summary": "### Impact 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. (`resources/read` was the only surface that already guarded this.) ### Patches Fixed in **1.3.1** (the fix was developed on the `v1.3.0` tag, which never published to npm; 1.3.1 is the first published release with the fix). Upgrade to `>= 1.3.1`. ### Workarounds Run a single vault per server process, or isolate each tenant on a separate process/credential. ### Fix A central `input.vault === ctx.vaultId` guard was added in dispatch before the scope check.",
"evidence": "osv:GHSA-84c9-qqpq-2pq5",
"products": [
{
"name": {
"value": "obsidian-tc",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.3.1",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "critical",
"structured": {
"id": "GHSA-84c9-qqpq-2pq5",
"aliases": [
"CVE-2026-77366",
"GHSA-84c9-qqpq-2pq5"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.3.1"
}
]
}
],
"package": {
"name": "obsidian-tc",
"purl": "pkg:npm/obsidian-tc",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-84c9-qqpq-2pq5/GHSA-84c9-qqpq-2pq5.json"
}
}
],
"modified": "2026-10-23T17:45:03.913249027Z",
"provider": "osv",
"references": [
"https://github.com/The-40-Thieves/obsidian-tc/security/advisories/GHSA-84c9-qqpq-2pq5",
"https://github.com/The-40-Thieves/obsidian-tc/pull/72",
"https://github.com/The-40-Thieves/obsidian-tc/commit/38b4992e87dc2715564236e1a42d005ab05a0194",
"https://github.com/The-40-Thieves/obsidian-tc",
"https://github.com/The-40-Thieves/obsidian-tc/releases/tag/v1.3.1",
"https://nvd.nist.gov/vuln/detail/cve-2026-77366"
],
"provider_metadata": {
"cwe_ids": [
"CWE-639",
"CWE-863"
],
"severity": "CRITICAL",
"github_reviewed": true,
"nvd_published_at": "2026-10-12T18:17:23Z",
"github_reviewed_at": "2026-10-23T17:29:17Z"
}
},
"related_cves": [
{
"value": "CVE-2026-77366",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 416471,
"published_at": "2026-10-23T17:29:17+00:00"
}