91 matches found
Authorization Bypass
obsidian-tc is vulnerable to authorization bypass. The vulnerability is due to insufficient validation of the caller-controlled vault identifier, missing vault binding in JWTs, and globally shared folder access controls, which allows an attacker with a valid token to read, modify, or delete...
Missing Origin Validation
obsidian-tc is vulnerable to missing Origin and DNS-rebinding validation. The vulnerability is due to missing Host, Origin, and DNS-rebinding validation in the Streamable HTTP transport when authentication is disabled, which allows an attacker to exploit a malicious webpage to gain unrestricted...
Obsidian-tc HTTP Transport Lacks Origin/DNS-rebinding Protection, Enabling Drive-by Vault Access On Loopback
Impact The Streamable HTTP transport was constructed without "enableDnsRebindingProtection"/"allowedHosts"/"allowedOrigins" and performed no "Origin"-header validation. With the documented "auth.mode: "none"" loopback default, a drive-by web page could "POST http://127.0.0.1/mcp" and receive call...
Obsidian-tc: Default Folder ACL Is Fail-open; .obsidian Plugin Secrets Are Readable By Default
Impact With a default configuration, an undefined "readPaths"/"writePaths" meant allow-all, the "strictReadDefault" flag was inert, and the ".obsidian"/".git"/".trash" control directories were denied only during enumeration — not on the direct request path. A caller could read...
Obsidian-tc : Symlink Read-ACL Scope Bypass Via Lexical Path Checks
Impact ACL checks ran on the lexical vault-relative path while containment used the realpath. An in-vault symlink placed under an allowed glob, whose realpath resolved into a denied folder, passed the read ACL — an intra-vault read-ACL-scope bypass. It requires an out-of-band-planted symlink no M...
Obsidian-tc Tokens Can Access Arbitrary Configured Vaults
Impact Tool dispatch did not check the caller-supplied "input.vault" against the caller's bound vault "ctx.vaultId"; the folder ACL was a single global instance and the JWT carried no vault claim. As a result, any valid token could read, write, or delete any configured vault by passing...
Obsidian-tc Bridge Tools Leak Denied-note Data Via Unfiltered Sibling Fields
Impact Bridge tool results filtered only the "items" array against the read ACL and passed sibling fields through unfiltered: "tasksfilter" emitted "groups" whose counts reflected denied notes, "makemdquery" returned "...result" siblings, and "listtemplates" enumerated Templater template paths an...
obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes
Summary createentity, linkentities, renameentity, unlinkentities and deleteentity regenerate a memory note's body from SQLite at the computed memory//.md path. When a note already existed at that path and was not owned by the entity being written a hand-authored note, or an orphan left by a...
npm: obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes
npm: obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes vulnerability discovered by ? in WordPress npm obsidian-tc versions = 1.0.1, = 1.31.3...
GHSA-R3G7-R4HR-M258 obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes
Summary createentity, linkentities, renameentity, unlinkentities and deleteentity regenerate a memory note's body from SQLite at the computed memory//.md path. When a note already existed at that path and was not owned by the entity being written a hand-authored note, or an orphan left by a...
obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback
Impact The Streamable HTTP transport was constructed without enableDnsRebindingProtection/allowedHosts/allowedOrigins and performed no Origin-header validation. With the documented auth.mode: "none" loopback default, a drive-by web page could POST http://127.0.0.1/mcp and receive caller http-loca...
npm: obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback
npm: obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback vulnerability discovered by ? in WordPress npm obsidian-tc versions 1.3.1...
EUVD-2026-97733
obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback...
GHSA-PQH8-4PJ7-32XX obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback
Impact The Streamable HTTP transport was constructed without enableDnsRebindingProtection/allowedHosts/allowedOrigins and performed no Origin-header validation. With the documented auth.mode: "none" loopback default, a drive-by web page could POST http://127.0.0.1/mcp and receive caller http-loca...
obsidian-tc Bridge tools leak denied-note data via unfiltered sibling fields
Impact Bridge tool results filtered only the items array against the read ACL and passed sibling fields through unfiltered: tasksfilter emitted groups whose counts reflected denied notes, makemdquery returned ...result siblings, and listtemplates enumerated Templater template paths and parsed...
GHSA-43R2-C7G8-PRC8 obsidian-tc Bridge tools leak denied-note data via unfiltered sibling fields
Impact Bridge tool results filtered only the items array against the read ACL and passed sibling fields through unfiltered: tasksfilter emitted groups whose counts reflected denied notes, makemdquery returned ...result siblings, and listtemplates enumerated Templater template paths and parsed...
npm: obsidian-tc Bridge tools leak denied-note data via unfiltered sibling fields
npm: obsidian-tc Bridge tools leak denied-note data via unfiltered sibling fields vulnerability discovered by ? in WordPress npm obsidian-tc versions 1.3.1...
EUVD-2026-98689
obsidian-tc Bridge tools leak denied-note data via unfiltered sibling fields...
npm: obsidian-tc: Declined human-in-the-loop confirmations can permit destructive calls over HTTP
npm: obsidian-tc: Declined human-in-the-loop confirmations can permit destructive calls over HTTP vulnerability discovered by ? in WordPress npm obsidian-tc versions = 1.13.0, = 1.31.3...
GHSA-737X-CWFR-5VVC obsidian-tc: Declined human-in-the-loop confirmations can permit destructive calls over HTTP
Summary On a Streamable HTTP deployment with auth.jwtSecret configured, serving a 2026-07-28-era client that declared elicitation.form support, a call to a dispatch-gated tool destructive: true, or a scope with an HITL floor that was offered an inputRequired confirmation could still complete afte...