Skip to main content
Menu
CVEs

CVE

obsidian-sync-mcp remote note tampering via DNS rebinding in MCP server

Only affects obsidian-sync-mcp 0.5.6 and earlier when run without MCP_AUTH_TOKEN (no-auth mode). Fixed in 0.5.7.

CVE-2026-77283Published Updated Summary written by a model

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.5.7
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Server runs without MCP_AUTH_TOKEN (no-auth mode) Affected versions are 0.5.6 and earlier A victim operator must visit a malicious web page while the server is running

Summary

obsidian-sync-mcp, an MCP server that gives AI agents access to Obsidian vaults, can be abused in deployments that run without an auth token. A malicious website visited by the operator can read, create, overwrite, delete, or move notes in the vault. An attacker can reach the server remotely, without logging in, through DNS rebinding or a cross-origin request, but only after the operator visits the malicious site.

Original description

obsidian-sync-mcp is an MCP server that gives AI agents access to Obsidian vaults. Prior to 0.5.7, deployments running without MCP_AUTH_TOKEN install no serverOptions.authenticate check for the HTTP /mcp endpoint, so requests are dispatched without validating the Host or Origin headers. A malicious website visited by the operator can use DNS rebinding to reach loopback, LAN, VPN, or container-published addresses, or directly issue a cross-origin request to loopback, and invoke the MCP tool surface to read, create, overwrite, delete, or move vault notes. Deployments using MCP_AUTH_TOKEN are not affected because browsers do not attach the bearer token. This issue is fixed in version 0.5.7.

Who should check

Operators running obsidian-sync-mcp 0.5.6 or earlier without MCP_AUTH_TOKEN, including the README filesystem quickstart and default docker-compose setups, on machines where a browser is used.

Not fixed by: Setting MCP_ALLOWED_HOSTS alone is not the fix; upgrade to 0.5.7.

“Any deployment running without MCP_AUTH_TOKEN — including the README "Filesystem mode (simplest)" quickstart and the self-hosted docker-compose setup”

github.com

cve.now Index

21Pcve.now Index 21 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active

What to do

  • Check whether your setup matches what the bug needs.

    Server runs without MCP_AUTH_TOKEN (no-auth mode) Affected versions are 0.5.6 and earlier A victim operator must visit a malicious web page while the server is running
  • Upgrade to a fixed version: 0.5.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77283 (obsidian-sync-mcp: Missing Host/Origin validation lets a public website drive a victim's Obsidian vault via DNS rebinding (no-auth mode)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77283 (entry last updated 2026-11-18):
Affected:
- es617 obsidian-sync-mcp: fixed in 0.5.7
Fixed versions: 0.5.7.
Conditions (all must be true for the bug to be hit):
- Server runs without MCP_AUTH_TOKEN (no-auth mode) (source: https://github.com/es617/obsidian-sync-mcp/security/advisories/GHSA-mx6p-3fg7-v6pj)
- Affected versions are 0.5.6 and earlier (source: https://github.com/es617/obsidian-sync-mcp/security/advisories/GHSA-mx6p-3fg7-v6pj)
- A victim operator must visit a malicious web page while the server is running (source: https://github.com/es617/obsidian-sync-mcp/security/advisories/GHSA-mx6p-3fg7-v6pj)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-77283 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77283 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/es617/obsidian-sync-mcp/security/advisories/GHSA-mx6p-3fg7-v6pj
- https://github.com/es617/obsidian-sync-mcp/commit/d4d2cbbb02ffadaecf1d6252902b8d08610c7018
- https://github.com/es617/obsidian-sync-mcp/releases/tag/v0.5.7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77283
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77283"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • es617 obsidian-sync-mcp

    fixed in 0.5.7

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · es617/obsidian-sync-mcp · Advisory GHSA-mx6p-3fg7-v6pj
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77283
RecordNVD · CVE-2026-77283
Other links 2
RepositoryGitHub · es617/obsidian-sync-mcp · Commit d4d2cbbb
RepositoryGitHub · es617/obsidian-sync-mcp · Release v0.5.7

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-77283

Is CVE-2026-77283 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A malicious web page that the operator visits while the server is running can use DNS rebinding to reach the local server. The page's JavaScript can then read the entire vault and create, overwrite, delete, or move notes, with no credentials and no prompt.Source: github.com

Which versions are affected by CVE-2026-77283?

obsidian-sync-mcp: before 0.5.7.Source: cve.now feed data

Am I affected, and how do I check?

Versions 0.5.6 and earlier, when the server runs without MCP_AUTH_TOKEN, the documented no-auth mode for local use. To check, look at the installed obsidian-sync-mcp version and whether MCP_AUTH_TOKEN is set in the environment where the server runs.Source: github.com

How do I fix CVE-2026-77283?

Upgrade to obsidian-sync-mcp 0.5.7, the fixed version.Source: github.com

More CVEs