CVE-2026-77363: DNS-rebinding vulnerability in obsidian-tc MCP server
obsidian-tc
The obsidian-tc Model Context Protocol server lacked transport header validation, allowing malicious web pages to gain unauthorized local vault access. Version 1.3.1 addresses this flaw.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 9.6
- EPSS
- <0.01 · top 96% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 12 Oct 2026
- last update
- 12 Oct 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-10-12CVE-2026-77363: obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults.NVD · nvd.nist.gov/vuln/detail/CVE-2026-77363
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- tags
- mcpdns-rebinding
- dates
- happened 12 Oct 2026 · first reported 12 Oct 2026
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 06:33Z · updated 2026-10-18 06:33Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2026-77363: DNS-rebinding vulnerability in obsidian-tc MCP server https://gcdradar.vercel.app/incidents/cve-2026-77363-dns-rebinding-vulnerability-in-obsidian-tc-mc · AIR-2026-0295 · closed 2026-10-12 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-10-12 - AI role: Attack on AI - Products: obsidian-tc - CVE ids: CVE-2026-77363 - CVSS: 9.6 ## Summary The obsidian-tc Model Context Protocol server lacked transport header validation, allowing malicious web pages to gain unauthorized local vault access. Version 1.3.1 addresses this flaw. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-10-12: CVE-2026-77363: obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. (https://nvd.nist.gov/vuln/detail/CVE-2026-77363) ## Sources - 2026-10-12 NVD: CVE-2026-77363: obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. https://nvd.nist.gov/vuln/detail/CVE-2026-77363 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed7.1obsidian-tc CVE-2026-115478: obsidian-tc MCP server suffers from path materialization flaw
Patch now · Disclosed · since 23 Oct 2026 · CVE-2026-115478
AI - closed7.1obsidian-tc CVE-2026-115477: obsidian-tc MCP server bypasses user confirmation check
Patch now · Disclosed · since 23 Oct 2026 · CVE-2026-115477
AI - closed4.7obsidian-tc CVE-2026-77361: obsidian-tc MCP server symlink path traversal vulnerability
Patch now · Disclosed · since 13 Oct 2026 · CVE-2026-77361
AI - closed4.3obsidian-tc CVE-2026-77362: obsidian-tc MCP server access control bypass vulnerability
Patch now · Disclosed · since 13 Oct 2026 · CVE-2026-77362
AI - closed6.5obsidian-tc CVE-2026-77364: Information disclosure vulnerability in obsidian-tc MCP server
Patch now · Disclosed · since 12 Oct 2026 · CVE-2026-77364
AI - closed9.9obsidian-tc CVE-2026-77366: Access control flaw in obsidian-tc Model Context Protocol server
Patch now · Disclosed · since 12 Oct 2026 · CVE-2026-77366
AI