The vulnerability allows an authenticated caller to read files in control directories (.obsidian, .git, .trash) and other vault data. Because readPaths and writePaths default to wildcards and strictReadDefault is not applied to direct requests, an attacker can retrieve sensitive artifacts such as plugin API keys and Obsidian Sync passwords. This constitutes a confidentiality breach, exposing in‑vault secrets to anyone who can authenticate to the server.

The affected product is obsidian‑tc, a server component from The‑40‑Thieves that implements the Model Context Protocol for Obsidian vaults. Versions prior to 1.3.1 are vulnerable; the issue is resolved in v1.3.1 and later where control directories are denied by default and strictReadDefault is enforced.

The CVSS score of 6.5 indicates moderate severity, with no EPSS data available and no listing in the CISA KEV catalog. The attack requires authentication to the obsidian‑tc service, but once authenticated, the attacker can perform direct path reads without enumeration constraints. The exploit can expose privileged data, raising risk for confidentiality. Administrators should assume the vulnerability is likely to be leveraged in environments where the service is exposed to untrusted users.