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…

在 GitHub Advisory Database 阅读

2026/10/24 03:29，GitHub Advisory Database 发布了“obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback”（类型：漏洞公告）。严重程度为“严重”（critical）。相关技术：JavaScript / Node.js。CVE：CVE-2026-77363。