High
obsidian-sync-mcp missing authentication on /mcp endpoint
An attacker can use DNS rebinding or cross-origin requests to reach the local MCP server and read, create, overwrite, delete, or move Obsidian vault notes. Only deployments without MCP_AUTH_TOKEN are vulnerable.
Source
Get the fix in TelegramGet the fix
FixLane has a reviewed fix procedure for this incident: a read-only check first, then the fix. Ask the Telegram bot, or connect an AI agent to the FixLane MCP server and call get_fix_prompt with incident id 3960 and your operating system.