obsidian-sync-mcp 0.5.7 fixes flaw that exposed unauthenticated Obsidian vaults

  • obsidian-sync-mcp
  • DNS rebinding
  • no-auth
  • CORS

Missing header validation allowed DNS rebinding attacks

Update to version 0.5.7 to secure Obsidian vaults

Deployments using authentication tokens remain unaffected

The maintainers of obsidian-sync-mcp fixed a vulnerability in version 0.5.7 that could let a website access a user’s Obsidian vault when the software ran without authentication. The advisory does not give the release date.

The flaw affects versions 0.5.6 and earlier. Without the MCP_AUTH_TOKEN authentication setting, a website visited while the server is running could read vault contents and create, overwrite, delete or move notes. The vulnerability also applied to vaults stored in CouchDB through Self-hosted LiveSync.

Version 0.5.7 checks Host and Origin headers in unauthenticated mode, rejecting browser requests that do not meet its allowed-host rules. The maintainers say deployments using MCP_AUTH_TOKEN are not affected; they recommend setting it on untrusted networks because non-browser clients can forge those headers. Setting the token also provides a workaround for all versions.