CVE-2026-77283
obsidian-sync-mcp is an MCP server that gives AI agents access to …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/es617/obsidian-sync-mcp/commit/d4d2cbbb02ffadaecf1d6252902b8d08610c7018
- github.com/es617/obsidian-sync-mcp/releases/tag/v0.5.7
- github.com/es617/obsidian-sync-mcp/security/advisories/GHSA-mx6p-3fg7-v6pj
- nvd.nist.gov/vuln/detail/CVE-2026-77283
- github.com/advisories/GHSA-mx6p-3fg7-v6pj
- nvd.nist.gov/vuln/detail/CVE-2026-77283
- cve.org/CVERecord?id=CVE-2026-77283
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.