CVE-2026-54618 PUBLISHED

Obsidian Web MCP: Unauthenticated vault access: /oauth/authorize auto-approves without authenticating the user

Assigner: GitHub_M
Reserved: 15.06.2026 Published: 17.09.2026 Updated: 17.09.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
CVSS Score: 9.4

Product Status

Vendor jimprosser
Product obsidian-web-mcp
Versions
  • Version < 0.2.0 is affected

References

Problem Types

  • CWE-306: Missing Authentication for Critical Function CWE
  • CWE-522: Insufficiently Protected Credentials CWE
  • CWE-601: URL Redirection to Untrusted Site ('Open Redirect') CWE