← AI agent vulnerabilities

CVE-2026-77366

obsidian-tc

9.9
Severity
Critical
Published
October 12, 2026
Last modified
October 16, 2026

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.

CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Weakness

References

CVE-2026-77366 on NVD

Listed in

CriticalMCP serversMissing authorization

More obsidian-tc CVEs

Oct 13
CVE-2026-773624.3

Bridge tools do not consistently apply the read access-control list (ACL) to every returned field.

Oct 13
CVE-2026-773614.7

Read access-control list (ACL) checks use a lexical vault-relative path while containment checks use the resolved path.

Oct 12
CVE-2026-773646.5

Undefined readPaths and writePaths settings allow all paths, strictReadDefault does not protect direct requests, and the .obsidian, .git, and .trash control directories are excluded only during enumeration.

Oct 12
CVE-2026-773638.8

The Streamable HTTP transport does not validate the Host or Origin header or enable DNS-rebinding protection.