ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-77366

obsidian-tc tokens can access arbitrary configured vaults

Published Oct 23, 2026 · catalog updated Oct 23, 2026 · obsidian-tc tokens can access

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-77366. EPSS is 0.31%. Act only if a listed version of obsidian-tc tokens can access is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (obsidian-tc tokens can access).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.31%
Remediation
Version ranges on file
Affected products
npm obsidian-tc

### Impact Tool dispatch did not check the caller-supplied against the caller's bound vault ( ); 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 , defeating multi-tenant isolation across ~90 tool sites. ( was the only surface that already guarded this.) ### Patches Fixed in **1.3.1** (the fix was developed on the tag, which never published to npm; 1.3.1 is the first published release with the fix). Upgrade to . ### Workarounds Run a single vault per server process, or isolate each tenant on a separate process/credential. ### Fix A central guard was added in dispatch before the scope check.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm obsidian-tc0 → 1.3.1
  • npm obsidian-tc< 1.3.1

How to fix CVE-2026-77366

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-77366. EPSS is 0.31%. Act only if a listed version of obsidian-tc tokens can access is installed.

Which versions are affected?

Compare what you have installed with 0 → 1.3.1, < 1.3.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-639: Authorization Bypass Through User-Controlled Key; CWE-863: Incorrect Authorization. EPSS 0.31%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 23, 2026 · GitHub Advisory Database

    Detected

    ### Impact Tool dispatch did not check the caller-supplied against the caller's bound vault ( ); 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 , defeating multi-tenant isolation across ~90 tool sites. ( was the only surface that already guarded this.) ### Patches Fixed in

  2. Oct 23, 2026 · GitHub Advisory Database

    Fix available

    obsidian-tc fixed in 1.3.1

  3. Oct 23, 2026 · GitHub Advisory Database

    Fix available

    obsidian-tc fixed in 1.3.1

  4. Oct 23, 2026 · GitHub Advisory Database

    Updated

    ### Impact Tool dispatch did not check the caller-supplied against the caller's bound vault ( ); 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 , defeating multi-tenant isolation across ~90 tool sites. ( was the only surface that already guarded this.) ### Patches Fixed in

Sources

  • CVE.orgVulnerability recordCVE-2026-77366

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-77366

    30-day exploitation probability 0.31%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-84c9-qqpq-2pq5

    obsidian-tc tokens can access arbitrary configured vaults

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-77366

    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 gua

    advisories.gitlab.com
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-84c9-qqpq-2pq5

    obsidian-tc tokens can access arbitrary configured vaults

    osv.dev

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 28, 2026
  • GitLab Advisory DatabaseOct 27, 2026
  • CVE.orgOct 23, 2026
  • GitHub Advisory DatabaseOct 23, 2026
  • OpenSSF OSV / OSV ScannerOct 23, 2026