Obsidian Web MCP: Unauthenticated vault access: /oauth/authorize auto-approves without authenticating the user
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| jimprosser | obsidian-web-mcp | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Jimprosser | Obsidian-web-mcp |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.507% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jimprosser
Jimprosser obsidian-web-mcp |
|
| Vendors & Products |
Jimprosser
Jimprosser obsidian-web-mcp |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Obsidian Web MCP: Unauthenticated vault access: /oauth/authorize auto-approves without authenticating the user | |
| Weaknesses | CWE-306 CWE-522 CWE-601 |
|
| References |
|
|
| Metrics |
cvssV3_1
|