CVE-2026-115477

obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. From 1.13.0 until 1.31.4, on a Streamable HTTP deployment with `auth.jwtSecret` configured and a 2026-07-28-era client declaring `elicitation.form` support, a dispatch-gated tool call offered an `inputRequired` confirmation could still complete after the human declined or cancelled, or the elicitation response was omitted or malformed, provided the client echoed the validly bound `requestState` on resubmission. The server trusted an authentic, call-bound state as proof of approval even though that state was minted before the `elicitation/create` leg was asked and proved only that the resubmission belonged to the same call. A client behaving incorrectly or under an attacker's control could therefore execute dispatch-gated destructive vault operations without the human's approval, while still requiring the caller's ordinary tool permissions. Only tools marked `destructive: true` or requiring a scope with a human-in-the-loop floor were reachable through this bypass. The sixteen handler-side conditionally gated tools, including `write_note` overwrite and `move_note`, did not read elicitation state on the modern wire and let neither approval nor decline through that path. Affected deployments using stdio or leaving `auth.jwtSecret` unset instead used the CLI `elicit_token` fallback and did not offer this `requestState` round trip. The fix does not prevent a malicious client from reporting a fabricated approval, because the server cannot verify that the client displayed the form or that a human saw it. This issue is fixed in version 1.31.4.

• CWE-285
• CWE-863

• https://github.com/The-40-Thieves/obsidian-tc/blob/v1.31.4/CHANGELOG.md
• https://github.com/The-40-Thieves/obsidian-tc/commit/101c91c656e2c2b88bcf3696a5da035f8c032c71
• https://github.com/The-40-Thieves/obsidian-tc/issues/967
• https://github.com/The-40-Thieves/obsidian-tc/pull/969
• https://github.com/The-40-Thieves/obsidian-tc/releases/tag/v1.31.4
• https://github.com/The-40-Thieves/obsidian-tc/security/advisories/GHSA-737x-cwfr-5vvc
• https://github.com/The-40-Thieves/obsidian-tc/issues/967

Published

Oct 23, 2026

Last Modified

Oct 29, 2026

Status

Deferred

• Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-11545IBM WebSphere Application Server 8.5 and 9.0 could allow a r…3.7
• CVE-2026-115450External Control of Assumed-Immutable Web Parameter (CWE-472…7.1
• CVE-2026-115453Authorization Bypass Through User-Controlled Key (CWE-639) i…7.1
• CVE-2026-115454An excessive resource allocation issue in the remote workflo…5.3
• CVE-2026-115457baserCMS is a website development framework. In versions 5.0…7.1
• CVE-2026-11546IBM WebSphere Application Server - Liberty 17.0.0.3 through …9.8
• CVE-2026-115478obsidian-tc is a governed, agent-ready Model Context Protoco…7.1
• CVE-2026-115479baserCMS is a website development framework. In versions 5.2…5.3
• CVE-2026-11548IBM WebSphere Application Server 8.5 and 9.0, and and IBM We…4.8
• CVE-2026-115480baserCMS is a website development framework. In versions 5.0…5.3
• CVE-2026-115481baserCMS is a website development framework. Starting in ver…8.5
• CVE-2026-115482In lsquic before 4.9.0, the HTTP/3 implementation can use an…7.5