obsidian-tc
Affected
- introduced
0, fixed1.3.1(semver)
Fixed versions
1.3.1
Fix
- Fixed version
1.3.1npm install [email protected]
Advisory
Also known as: CVE-2026-77363
obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback
Impact
The Streamable HTTP transport was constructed without enableDnsRebindingProtection/allowedHosts/allowedOrigins and performed no Origin-header validation. With the documented auth.mode: "none" loopback default, a drive-by web page could `POST http://127.0.0.1/mcp` and receive caller http-local with scopes ["*"] — full vault read/write — via DNS rebinding / a forged Origin.
Patches
Fixed in 1.3.1. Upgrade to >= 1.3.1. The transport now enables DNS-rebinding protection and allowed hosts/origins and returns HTTP 403 on an invalid Origin (per MCP 2025-11-25).
Workarounds
Do not expose the HTTP transport with auth.mode: "none"; require JWT auth, or bind to a non-loopback interface behind a proxy that validates Origin.
Critical Basis: The source's own band: CRITICAL
0, fixed 1.3.1 (semver)1.3.1
1.3.1npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0