UTC
High

obsidian-sync-mcp: Missing Host/Origin validation lets a public website drive a victim's Obsidian vault via DNS rebinding (no-auth mode)

CVE-2026-77283 · GHSA-mx6p-3fg7-v6pj · published 2026-11-19

Severity
High
CVSS score
8.8
Chance of exploitation (EPSS)
0.38%
Fixed in
0.5.7
What it is

Any deployment running without MCP_AUTH_TOKEN — including the README "Filesystem mode (simplest)" quickstart and the self-hosted docker-compose setup (where MCP_AUTH_TOKEN defaults to empty)" — is exposed to any website the operator visits while the server is running. That page's JavaScript can silently read the entire vault and create/overwrite/delete/move notes, with no credentials and no prompt. In CouchDB/Self-hosted LiveSync mode, the same code path applies, so vault content in CouchDB is equally reachable. Deployments that set MCP_AUTH_TOKEN are not affected — a bearer token is not attached by browsers, so a forged request returns HTTP 401.

What to do

Upgrade obsidian-sync-mcp to 0.5.7 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Upgrade to 0.5.7, which validates both the Host and Origin headers in no-auth mode: any request whose Host is not localhost/127.0.0.1/::1 (or a value in the new MCP_ALLOWED_HOSTS), or that carries a cross-origin Origin not in that allowlist, is rejected before any MCP method runs. The Host check defeats DNS rebinding; the Origin check defeats the related bypass where a page directly fetches http://127.0.0.1: /mcp (genuine loopback Host, attacker Origin) — the transport's wildcard CORS would otherwise expose the response. Non-browser MCP clients send no Origin, so they are unaffected. …

Affected
PackageRegistryAffectedFixed in
obsidian-sync-mcpnpm<= 0.5.60.5.7
Downstream in the Official MCP Registry

1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.

  • io.github.es617/obsidian-sync-mcpobsidian-sync-mcp@0.5.2
See the trace →

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].