obsidian-sync-mcp: Missing Host/Origin validation lets a public website drive a victim's Obsidian vault via DNS
Affects obsidian-sync-mcpSource GCVE Database
Not known to be exploited · CVSS 8.8 High : upgrade to 0.5.7 soon.
Data as of 19 Nov 2026, 21:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.8 |
|---|
- Patch
- Available – fixed in 0.5.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade obsidian-sync-mcp to 0.5.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmobsidian-sync-mcp | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade obsidian-sync-mcp to version 0.5.7 or later, which enforces Host and Origin header validation in no-auth mode to block browser-based attacks. Alternatively, set MCP_AUTH_TOKEN to require authentication, which immediately closes the attack vector by rejecting unauthorized requests. These measures prevent malicious websites from exploiting DNS rebinding or cross-origin requests to access or modify vault contents. No other actions are required if these mitigations are applied.
Description
Obsidian-sync-mcp versions up to 0.5.6 running without MCP_AUTH_TOKEN (no-auth mode) do not validate Host or Origin headers, allowing malicious websites to exploit DNS rebinding or cross-origin requests to access and manipulate a user's Obsidian vault without authentication. This affects local network assumptions and exposes full read/write capabilities to attacker-controlled web pages. Version 0.5.7 patches this by validating Host and Origin headers to block such attacks. Deployments using MCP_AUTH_TOKEN are not affected.
References
- github.com/es617/obsidian-sync-mcp/security/advisories/GHSA-mx6p-3fg7-v6pj (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-77283 (opens in a new tab)
- github.com/es617/obsidian-sync-mcp/commit/d4d2cbbb02ffadaecf1d6252902b8d08610c7018 (opens in a new tab)
- github.com/es617/obsidian-sync-mcp (opens in a new tab)
- github.com/es617/obsidian-sync-mcp/releases/tag/v0.5.7 (opens in a new tab)