Vulnerabilidades de The-40-Thieves
CVEs publicadas que afetam produtos de The-40-Thieves: 5 registro(s), com severidade, exploração e correções.
CVE-2026-77362
Média · 4.3
CWE-200 13/10/2026
obsidian-tc bridge tools expose data outside the read ACL
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, bridge tools do not consistently apply the read access-control list (ACL) to every returned field. The tasks_filter tool exposes group counts derived from denied notes, makemd_query passes unfiltered sibling result fields through, and list_templates exposes template paths and parsed user-function bodies without a read-whitelist check. An authenticated caller can consequently infer or read data from notes outside the caller's read ACL. Version 1.3.1 fixes the vulnerability by filtering path-attributable fields and applying the read whitelist to list_templates.
CVE-2026-77361
Média · 4.7
CWE-59 13/10/2026
obsidian-tc symlink path mismatch bypasses read ACL restrictions
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, read access-control list (ACL) checks use a lexical vault-relative path while containment checks use the resolved path. An in-vault symlink under an allowed glob that resolves into a denied folder can therefore bypass the read ACL and expose files in the denied folder. Exploitation requires an out-of-band-planted symlink and does not permit an escape from the vault root. Version 1.3.1 fixes the vulnerability by applying ACL checks to the resolved vault-relative path.
CVE-2026-77366
Crítica · 9.9
CWE-639 12/10/2026
obsidian-tc: bypass de autorização na seleção de vault (IDOR)
obsidian-tc é um servidor Model Context Protocol governado e pronto para agentes, voltado a vaults do Obsidian. Antes da versão 1.3.1, o despacho de ferramentas não compara o valor input.vault, controlado pelo chamador, com o vault vinculado ao chamador; o JSON Web Token (JWT) não possui claim de vault; e a lista de controle de acesso de pastas é compartilhada globalmente. Assim, qualquer token válido pode selecionar outro vault configurado e ler, escrever ou apagar seu conteúdo por meio das ferramentas afetadas. A versão 1.3.1 corrige a vulnerabilidade ao vincular tokens e o contexto da requisição a um vault e ao rejeitar valores input.vault divergentes antes das verificações de escopo.
CVE-2026-77364
Média · 6.5
CWE-200 12/10/2026
obsidian-tc fail-open default ACL exposes Obsidian control-directory secrets
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, undefined readPaths and writePaths settings allow all paths, strictReadDefault does not protect direct requests, and the .obsidian, .git, and .trash control directories are excluded only during enumeration. An authenticated caller can directly read sensitive files such as .obsidian/plugins/*/data.json, potentially exposing plugin API keys, Obsidian Sync passwords, and other in-vault data. Version 1.3.1 fixes the vulnerability by denying the control directories by default and enforcing strictReadDefault on direct request paths.
CVE-2026-77363
Alta · 8.8
CWE-346 12/10/2026
obsidian-tc Streamable HTTP transport permits cross-origin loopback vault access
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, the Streamable HTTP transport does not validate the Host or Origin header or enable DNS-rebinding protection. When the documented loopback configuration uses auth.mode set to none, a malicious web page can send requests to the local MCP endpoint and receive unrestricted vault access through the http-local caller. Version 1.3.1 fixes the vulnerability by enabling host, origin, and DNS-rebinding validation.