CVE-2026-77363: obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback
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.
References
- github.com/The-40-Thieves/obsidian-tc/commit/6428bfe6fdfd43aa7b4b369be3aecd6a268fb928
- github.com/The-40-Thieves/obsidian-tc/pull/74
- github.com/The-40-Thieves/obsidian-tc/releases/tag/v1.3.1
- github.com/The-40-Thieves/obsidian-tc/security/advisories/GHSA-pqh8-4pj7-32xx
- github.com/advisories/GHSA-pqh8-4pj7-32xx
- nvd.nist.gov/vuln/detail/CVE-2026-77363
- nvd.nist.gov/vuln/detail/cve-2026-77363
Code Behaviors & Features
Detect and mitigate CVE-2026-77363 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →