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.
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.
How to check
- Run npm ls obsidian-sync-mcp (and npm ls -g) and check your MCP client config for the version it launches.
- Check whether MCP_AUTH_TOKEN is set in your environment or docker-compose file.
How to fix
- Upgrade obsidian-sync-mcp to 0.5.7 or later.
- Set MCP_AUTH_TOKEN even for local use.
- 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 Sources
- criticalCVE-2026-76807: Doist's official Todoist MCP HTTP server let any website use DNS rebinding to read, create and delete your Todoist data (fixed 10.3.3)
- criticalCVE-2026-77359: Jupyter MCP Server's /api/connect and /api/stop routes skipped the token and Origin checks, so a website or network caller could repoint it to an attacker's Jupyter backend (fixed 1.0.3)
- criticalMalicious npm package @guicai777/mcp-doctor posed as an MCP diagnostic tool and dropped a hidden Windows executable, with a README telling users to run mshta (MAL-2026-20295)
- criticalMalicious npm packages posing as AI SDKs and MCP servers: character-ai-sdk, char-ai-sdk, @mibbp/agent-observer, mrnima-openai-chatgpt-bot and @fdcasj_dfew/md-doc-mcp
- criticalMalicious AI agent and MCP packages: mcp-aevo-server (PyPI) steals Aevo trading keys and wallet private keys; vamp-mcp, tsc-ai and @tnhorg/agent-skills (npm) flagged as malware
- criticalMalicious npm packages posing as MCP servers and AI APIs: @shadowdu/memos-mcp, @shadowdqj/image-mcp, mem0-mcp-server and ai-apis