Jimprosser obsidian-web-mcp
Obsidian Web MCP: Unauthenticated vault access: /oauth/authorize auto-approves without authenticating the user
Obsidian Web MCP is a secure remote MCP server for Obsidian vaults. Prior to 0.2.0, /oauth/authorize issues an authorization code without a login, consent, or session check, and /oauth/token can exchange that code for the static VAULT_MCP_TOKEN without authenticating a client. An unauthenticated remote caller who can reach the intended tunnel deployment can therefore call /mcp and use vault_read, vault_write, vault_search, vault_list, vault_move, and vault_delete against the entire vault. Optional PKCE does not prevent an attacker-initiated flow, and unauthenticated /oauth/register also exposes a client_credentials path by returning the configured VAULT_OAUTH_CLIENT_SECRET. This issue is fixed in version 0.2.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.2.0
Fixed in 0.2.0
Mitigation
Upgrade obsidian-web-mcp to 0.2.0 or later.
References
- Vendor advisory github.com/jimprosser/obsidian-web-mcp/securit…
- Patch github.com/jimprosser/obsidian-web-mcp/pull/30
- Patch github.com/jimprosser/obsidian-web-mcp/commit/…
1 more
- Release notes github.com/jimprosser/obsidian-web-mcp/release…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.