AI Stack Alert High CVE-2026-77283 For AppSec, AI Eng, SOC / IR AI-assisted
CVE-2026-77283: obsidian-sync-mcp before 0.5.7 exposes vault tools to DNS rebinding and cross-origin requests
obsidian-sync-mcp is an MCP server that gives AI agents access to Obsidian vaults. Prior to version 0.5.7, deployments without MCP_AUTH_TOKEN do not validate Host or Origin headers on the HTTP /mcp endpoint. A malicious website visited by the operator can use DNS rebinding or cross-origin requests to invoke MCP tools that read, create, overwrite, delete, or move vault notes.
Why it matters
Operators running the server without an auth token can have their Obsidian vault notes read, modified, or deleted by any website they visit in a browser. Deployments that use MCP_AUTH_TOKEN are not affected.
Do this
- Upgrade obsidian-sync-mcp to version 0.5.7 or later.
- Until patched, set MCP_AUTH_TOKEN on all deployments so that the HTTP /mcp endpoint requires a bearer token.
- Inventory hosts running obsidian-sync-mcp, including loopback, LAN, VPN, and container-published bindings, and confirm their version.
- Review vault backups and version history for unexpected overwrites, deletions, or moves after exposure.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 8.8CVSS
- NoPublic PoC
- 36/100Priority
- 80%Confidence
Evidence
“Prior to 0.5.7, deployments running without MCP_AUTH_TOKEN install no serverOptions.authenticate check for the HTTP /mcp endpoint”
“A malicious website visited by the operator can use DNS rebinding to reach loopback, LAN, VPN, or container-published addresses”
“Deployments using MCP_AUTH_TOKEN are not affected because browsers do not attach the bearer token.”
Sources
Affected / related
obsidian-sync-mcp, DNS rebinding
Published 2026-11-18 23:17 UTC · updated 2026-11-19 00:35 UTC · AI-assisted summary, checked against quoted sources · How we score