AAK-MCP-OBSIDIANTC-CVE-2026-115477-001: obsidian-tc from 1.0.1 below 1.31.4: a declined confirmation can still run a destructive call, and memory tools overwrite notes they do not own
- Severity
- HIGH
- 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
ObsidianTcDeclinedElicitationAndNoteOwnership
What it detects
obsidian-tc, an MCP server for Obsidian vaults published on npm as obsidian-tc and as the image ghcr.io/the-40-thieves/obsidian-tc, has two flaws fixed in 1.31.4. CVE-2026-115477 (1.13.0 to 1.31.3): on a Streamable HTTP deployment with auth.jwtSecret set and a client that supports form elicitation, a dispatch-gated tool call offered an inputRequired confirmation could still complete after the human declined or cancelled it, or sent no answer, because the server took an authentic, call-bound requestState echoed on resubmission as proof of approval; tools marked destructive: true, or needing a scope with a human-in-the-loop floor, were reachable that way (GHSA-737x-cwfr-5vvc). CVE-2026-115478 (1.0.1 to 1.31.3): create_entity, link_entities, rename_entity, unlink_entities and delete_entity rewrote memory notes at their computed path without checking who owned the note there, so a hand-written note or another entity's orphan whose name sanitized to the same path lost its body, and several of them changed SQLite before filesystem work that could fail, leaving the memory graph out of step with the notes (GHSA-r3g7-r4hr-m258). Both are CVSS 4.0 7.1. 1.31.4 refuses to touch a note the entity does not own, checks ownership before any write, and no longer takes the echoed state as an answer.
How to fix
Upgrade obsidian-tc (npm or the GHCR image) to 1.31.4 or later and pin it. Until then serve it over stdio, which uses the CLI elicit_token path rather than the HTTP requestState round trip, and enable snapshots so restore_note can recover a note the memory tools overwrote.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-OBSIDIANTC-CVE-2026-115477-001
Limitations
Reports obsidian-tc from 1.0.1 below 1.31.4 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.31.4 in compose files, Kubernetes manifests, Helm values, Dockerfiles and MCP configs. CVE-2026-115477 needs 1.13.0 or later, the HTTP transport and auth.jwtSecret, none of which the rule reads, so 1.0.1 to 1.12.x and stdio-only installs are reported although only CVE-2026-115478 reaches them. latest was 1.33.1 and states no version, so an unpinned npx -y obsidian-tc and the image's latest are not reported. Releases below 1.3.1 also fire AAK-MCP-OBSIDIANTC-CVE-2026-77366-001. The 0.0.1 placeholder is not reported. 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-115477, CVE-2026-115478
- OWASP MCP Top 10: MCP07:2025 (Insufficient Authentication & Authorization), MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
- OWASP Agentic Top 10: ASI09 (Human-Agent Trust Exploitation), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-SUPPLY-08 (MCP-Specific Vuln)
- CSA AI Controls Matrix (AICM): IAM-01, 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-115477-001.md: the page then shows that text, with the registry reference appended under it.