# CVE-2026-77361: obsidian-tc symlink path mismatch bypasses read ACL restrictions

> An attacker can bypass read ACL restrictions in obsidian-tc by using a symlink to access files in denied folders within the vault.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-c5xx-h28h-f682

## What is CVE-2026-77361?

CVE-2026-77361 is a medium-severity path traversal vulnerability in The-40-Thieves obsidian-tc, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization), CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-77361?

2 open source packages ship an affected version, including obsidian-tc.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `obsidian-tc` | npm | All versions | 1.3.1 |
| `obsidian-tc` | npm | All versions | 1.3.1 |

## How do I fix CVE-2026-77361?

Upgrade obsidian-tc to 1.3.1 or later.

## Is CVE-2026-77361 being exploited?

There is no known exploitation of CVE-2026-77361 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77361 and fix it if it is affected.

What it is: CVE-2026-77361 is a medium-severity path traversal vulnerability in The-40-Thieves obsidian-tc, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77361 in the wild and no public exploit code.

Affected packages and fixed versions:
- obsidian-tc (npm): affected all versions; fixed in 1.3.1
- obsidian-tc (npm): affected all versions; fixed in 1.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77361/ (Markdown: https://insights.sbomify.com/CVE-2026-77361/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77361
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77361
- OSV: https://osv.dev/vulnerability/CVE-2026-77361

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77361/
Summaries are generated and may contain mistakes; the official description above is the record.