AAK-MCP-OBSIDIANTC-CVE-2026-77366-001: obsidian-tc below 1.3.1: any HTTP token reaches every configured vault, the HTTP transport answers cross-origin requests, and the read ACL leaks
- Severity
- CRITICAL
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/container_image_pins.py,agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
ObsidianTcVaultBindingAndOriginBypass
What it detects
obsidian-tc is an MCP server for Obsidian vaults, published on npm as obsidian-tc and as the image ghcr.io/the-40-thieves/obsidian-tc. Every release below 1.3.1 (1.0.1, 1.0.2 and 1.2.1) carries five disclosed defects that one upgrade fixes. CVE-2026-77366 (CRITICAL 9.9): tool dispatch never compares a call's vault argument with the caller's vault, the JWT has no vault claim and the folder ACL is global, so any valid HTTP token reads, writes or deletes every configured vault. CVE-2026-77363 (HIGH 8.8): the Streamable HTTP transport checks neither Host nor Origin, so with the documented loopback setup and auth.mode: "none" a web page drives the endpoint as the all-scopes http-local caller. CVE-2026-77364 (MEDIUM 6.5): an undefined readPaths or writePaths allows every path, and .obsidian, .git and .trash are hidden only from listings, so a caller reads plugin API keys and Sync passwords from .obsidian/plugins/*/data.json by path. CVE-2026-77361 (MEDIUM 4.7): read-ACL checks use the lexical path, so an in-vault symlink under an allowed folder reads a denied one. CVE-2026-77362 (MEDIUM 4.3): the tasks_filter, makemd_query and list_templates bridge tools return data from notes outside the caller's read ACL. The first two need the HTTP transport, which is off by default.
How to fix
Upgrade obsidian-tc (npm or the GHCR image) to 1.3.1 or later and pin it. Until then keep the HTTP transport off, or require JWT auth and run one vault per server process; set explicit readPaths and writePaths that leave out .obsidian, .git and .trash; and allow no untrusted symlinks in the vault. After upgrading, give each tenant's token a vault claim.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-OBSIDIANTC-CVE-2026-77366-001
Limitations
Reports obsidian-tc below 1.3.1, from 1.0.0 on, where a package.json, lockfile or MCP config states the version, reporting a range that admits an affected version, and ghcr.io/the-40-thieves/obsidian-tc tags below 1.3.1 in compose files, Kubernetes manifests, Helm values, Dockerfiles and MCP configs. An unpinned npx -y obsidian-tc, the README's own config, installs 1.33.1, the newest release on 2026-10-15, so it is not reported, and neither is the image's latest. The 0.0.1 placeholder and the scoped @the-40-thieves/obsidian-tc placeholder have no server and are not reported. The pin reads the version, not the transport setting, so a stdio-only install is reported too. The Claude Desktop bundle (.mcpb) and the Obsidian plugin are not read. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-77366, CVE-2026-77363, CVE-2026-77364, CVE-2026-77361, CVE-2026-77362
- OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP07:2025 (Insufficient Authentication & Authorization)
- OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-AUTH-01 (Missing Authentication)
- CSA AI Controls Matrix (AICM): IAM-01, IVS-04, STA-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-OBSIDIANTC-CVE-2026-77366-001.md: the page then shows that text, with the registry reference appended under it.