Secure Autonomous
FeedbackGet alertsCheck a deployment
Signals › SIG-2026-10-13-002

CVE-2026-77366: obsidian-tc

The National Vulnerability Database (NVD) record says that before obsidian-tc 1.3.1 any valid token could select another configured vault through Model Context Protocol (MCP) tool calls and read, write or delete its contents; 1.3.1 binds tokens and request context to a vault.

VulnerabilitySoftware agents · Enterprise work agentsRecord published 2026-10-12Posted 2026-10-13
SIG-2026-10-13-002National Vulnerability Database record ↗

The record

Kind
Vulnerability
Source record
CVE-2026-77366: obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, tool (National Vulnerability Database record)
Record published
2026-10-12
Posted here
2026-10-13
World
Software agents · Enterprise work agents
Controls concerned
Authority binding C-A2; Hard domain restriction C-E2
Checked
Checked against its record on 2026-10-22 by a reader who did not draft it; report verification/reports/SIG-2026-10-13-002-2026-10-22.md.

A signal's controls are the ones its record points at, the exposure; a case's controls are the ones its records show were absent or failed, so the two can differ.

Corrections

Changes to what this signal says, with the reason. Every earlier version is kept.

What a signal is. A signal records what a primary record says; it assigns no fault. It is lighter than a case: one dated item from one record, tagged with the world, sector and controls it touches. It becomes a case when it meets the bar for one.

New signals like this, once a week. A short email when a case, signal or rule touches software agents. Free; unsubscribe in one click.

Get the weekly email

Newer: CVE-2026-110202 to 110206: Roo Code
Older: CVE-2026-84318: Nginx UI

Is this wrong? Dispute it with the record that shows otherwise. All signals · RSS feed.

Help shape the Register

A person reads every answer; changes it leads to are logged in the methodology. To dispute a claim or reply for a named company, use Respond, dispute, or submit.

Did this page help with what you came to do?