obsidian-tc
Records
5
Disclosed CVEs
5
Exploited (sev 3–4)
0
CISA KEV flagged
0
Newest record 2026-10-13 · 5 distinct CVE ids · open in the explorer (the explorer matches the first product a record names, so it can list fewer)
Patch now: confirmed exploitation or KEV · 0
Records at severity 3–4 (exploitation confirmed by CISA, the vendor or reporting) and records flagged as listed in CISA KEV. The KEV flag is the classifier’s cisa-kev tag or a source on the KEV catalog; it is recorded when the collector sees the listing, so a missing flag does not mean a CVE is absent from the catalog.
No record for obsidian-tc has confirmed exploitation or a KEV flag.
Disclosures by month · last 24 months
█
Nov ’245 disclosed · peak 5 in Oct ’26Oct ’26
Disclosed CVEs, no confirmed exploitation · 5
- 2026-10-13CVE-2026-77361CVE-2026-77361: obsidian-tc MCP server symlink path traversal vulnerability2 Disclosedmcp-server · path-traversal
- 2026-10-13CVE-2026-77362CVE-2026-77362: obsidian-tc MCP server access control bypass vulnerability2 Disclosedmcp-server · access-control
- 2026-10-12CVE-2026-77363CVE-2026-77363: DNS-rebinding vulnerability in obsidian-tc MCP server2 Disclosedmcp · dns-rebinding
- 2026-10-12CVE-2026-77364CVE-2026-77364: Information disclosure vulnerability in obsidian-tc MCP server2 Disclosedmodel-context-protocol · information-disclosure
- 2026-10-12CVE-2026-77366CVE-2026-77366: Access control flaw in obsidian-tc Model Context Protocol server2 Disclosedmodel-context-protocol · access-control
This page lists what has been reported, not what to do about it. Versions and fixes are in each linked advisory; check the vendor’s own advisory before acting.