Vulnerability Description
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.
CVSS Score
CRITICAL
Related Weaknesses (CWE)
References
- https://github.com/jimprosser/obsidian-web-mcp/commit/e4924f096ee7494a7999d6c0cc
- https://github.com/jimprosser/obsidian-web-mcp/pull/30
- https://github.com/jimprosser/obsidian-web-mcp/releases/tag/v0.2.0
- https://github.com/jimprosser/obsidian-web-mcp/security/advisories/GHSA-hwhg-mrj
FAQ
What is CVE-2026-54618?
CVE-2026-54618 is a vulnerability with a CVSS score of 9.4 (CRITICAL). 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 excha...
How severe is CVE-2026-54618?
CVE-2026-54618 has been rated CRITICAL with a CVSS base score of 9.4/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-54618?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.