AI Stack Alert High For AppSec, AI Eng, SOC / IR Unconfirmed AI-assisted
obsidian-sync-mcp below 0.5.7: missing Host/Origin validation enables DNS rebinding in no-auth mode
The npm package obsidian-sync-mcp, versions below 0.5.7, does not validate Host or Origin headers. A public website can use DNS rebinding to drive a victim's Obsidian vault through the MCP server when no-auth mode is enabled. The advisory is rated high and is fixed in version 0.5.7.
Why it matters
Any user running an affected server in no-auth mode may have their local Obsidian notes read or modified by a malicious web page the user visits. Attackers gain access to vault contents without credentials.
Do this
- Upgrade the npm package obsidian-sync-mcp to version 0.5.7 or later.
- Until patched, disable no-auth mode and require authentication for the MCP server.
- Confirm the server binds only to localhost and review whether it is reachable from other hosts.
- Review MCP server logs for unexpected requests with foreign Host or Origin headers.
Signals
- NoCISA KEV
- 36/100Priority
- 80%Confidence
Evidence
“Package: npm:obsidian-sync-mcp, affected versions <0.5.7; fixed in 0.5.7.”
“Missing Host/Origin validation lets a public website drive a victim's Obsidian vault via DNS rebinding (no-auth mode)”
Sources
Affected / related
obsidian-sync-mcp, io.github.es617/obsidian-sync-mcp
Published 2026-11-19 20:41 UTC · updated 2026-11-20 00:35 UTC · AI-assisted summary, checked against quoted sources · Unconfirmed: single non-official source · How we score