CVE-2026-77283 · es617 / obsidian-sync-mcp
CVE-2026-77283 · Reported 18 Nov 2026
Full advisory details, affected packages, severity context, and original source.
Affected technology
Affected versions and fixes
Version information comes from OSV, NVD, and the CVE vendor record. Each source may describe a different package, release branch, or platform.
es617 / obsidian-sync-mcp
CVE vendor record- affected: < 0.5.7
Fixed releases / commits: Not explicitly provided by this source. Check the vendor guidance.
Advisory overview
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.
