obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback
影響: npm:obsidian-tc < 1.3.1 → 1.3.1
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 r…
Read on GitHub Advisory Database
| CVE | CVE-2026-77363 |
|---|---|
| Source | GitHub Advisory Database |
| Fetched | 10/24/2026, 03:42 AM |
| Data | Markdown JSON |
On 10/24/2026, 03:29 AM, GitHub Advisory Database published "obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback" (type: Advisory). Severity is "Critical" (critical). Related technologies: JavaScript / Node.js. CVE: CVE-2026-77363.