← All advisories
CVE-2026-77283highAgent hijacking2026-11-18

CVE-2026-77283: obsidian-sync-mcp in no-auth mode let any website use DNS rebinding to read, overwrite and delete your Obsidian vault notes (fixed 0.5.7)

obsidian-sync-mcp (npm), an MCP server that gives AI agents access to Obsidian vaults, did not check the Host or Origin header on its HTTP /mcp endpoint when run without MCP_AUTH_TOKEN, the documented no-auth mode for local use. Up to 0.5.6, a web page the operator visits can use DNS rebinding (or a direct cross-origin request to loopback) to call every tool and read the whole vault, or create, overwrite, delete and move notes, with no prompt. CouchDB / Self-hosted LiveSync mode is equally exposed. Fixed in 0.5.7.

01.

What it is

Without MCP_AUTH_TOKEN no serverOptions.authenticate check is installed, and requests are dispatched without validating Host or Origin (CWE-350). The reachable tools are read_note, write_note, edit_note, delete_note, move_note, list_notes, list_folders, list_tags and get_note_metadata.

Exposed setups include the README's "Filesystem mode (simplest)" quickstart and the self-hosted docker-compose setup, where MCP_AUTH_TOKEN defaults to empty. Loopback, LAN, VPN and container-published addresses can all be reached.

Deployments that set MCP_AUTH_TOKEN are not affected: browsers don't attach the bearer token, so forged requests get HTTP 401.

Affected: obsidian-sync-mcp <= 0.5.6. Version 0.5.7 (released 10 July 2026) validates Host and Origin in no-auth mode. GitHub published the advisory on 19 November 2026.

02.

How to check

  1. Run npm ls obsidian-sync-mcp (and npm ls -g) and check your MCP client config for the version it launches.
  2. Check whether MCP_AUTH_TOKEN is set in your environment or docker-compose file.
03.

How to fix

  1. Upgrade obsidian-sync-mcp to 0.5.7 or later.
  2. Set MCP_AUTH_TOKEN even for local use.
  3. If an affected server ran while you were browsing, compare your vault against a backup or its sync history for unexpected edits or deletions.
npm ls obsidian-sync-mcp; npm ls -g obsidian-sync-mcp
grep -n MCP_AUTH_TOKEN docker-compose.yml .env 2>/dev/null
04.

Sources

Related on VibeVulns
More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.