CVE-2026-77361

What it is

obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, read access-control list (ACL) checks use a lexical vault-relative path while containment checks use the resolved path. An in-vault symlink under an allowed glob that resolves into a denied folder can therefore bypass the read ACL and expose files in the denied folder. Exploitation requires an out-of-band-planted symlink and does not permit an escape from the vault root. Version 1.3.1 fixes the vulnerability by applying ACL checks to the resolved vault-relative path.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data exposure.

Exploit odds

0.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-10-13 14:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-16 22:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.1% in the next 30 days (EPSS).
• Severity: 4.7 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-10-13 14:17 UTC

Last modified

2026-10-16 22:17 UTC

Exploit probability

0.1% · EPSS, next 30 days

Weakness

CWE-59

Record status

Awaiting Analysis

Attack profile CVSS 3.1 · 4.7

Attack vector

Local

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-77361.md and follow it. Check whether this project is affected by CVE-2026-77361. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge