Skip to main content
CVE-2026-77283VulnerabilityPublished

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

0
Compare
Authoritative record:CVE-2026-77283· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 0.5.7 soon.

Data as of 19 Nov 2026, 21:06 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
npmobsidian-sync-mcpAffected
  • <0.5.7
Fixed in
  • 0.5.7

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

Community reviews

Loading reviews…