obsidian-sync-mcp unauthorized tool access in HTTP /mcp endpoint
es617 obsidian-sync-mcp
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| obsidian-sync-mcp npm |
|
|
Original description
obsidian-sync-mcp is an MCP server that gives AI agents access to Obsidian vaults. Prior to 0.5.7, deployments running without MCP_AUTH_TOKEN install no serverOptions.authenticate check for the HTTP /mcp endpoint, so requests are dispatched without validating the Host or Origin headers. A malicious website visited by the operator can use DNS rebinding to reach loopback, LAN, VPN, or container-published addresses, or directly issue a cross-origin request to loopback, and invoke the MCP tool surface to read, create, overwrite, delete, or move vault notes. Deployments using MCP_AUTH_TOKEN are not affected because browsers do not attach the bearer token. This issue is fixed in version 0.5.7.
From the CVE record · GitHub_M