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
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.
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. …
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| obsidian-sync-mcp | npm | <= 0.5.6 | 0.5.7 |
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
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
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.