GHSA-84c9-qqpq-2pq5: obsidian-tc (CVE-2026-77366)

Package	Ecosystem	Affected	Fixed in
obsidian-tc	npm	<1.3.1	1.3.1

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The npm package obsidian-tc, in versions before 1.3.1, does not check the vault named in a tool request against the vault bound to the caller's token. Any valid token can therefore read, write, or delete any configured vault by supplying a different vault identifier, which defeats tenant isolation. Upgrade to obsidian-tc 1.3.1 or later, which adds a central check in tool dispatch. The source also lists a workaround: run a single vault per server process, or give each tenant its own process or credential.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
9.9	Critical	3.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H	CNA (GitHub_M)

CISA KEV Not listed.
EPSS 0.0031, the 23rd percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

31 Oct 2026, 13:33 UTC First seen by agentprime
31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.