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…
| CVE | CVE-2026-77363 |
|---|---|
| 情報源 | GitHub Advisory Database |
| 取得日時 | 2026/10/24 03:42 |
| データ | Markdown JSON |
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。