<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Obsidian-Tc - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/obsidian-tc/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 23 Oct 2026 21:49:02 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/obsidian-tc/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Obsidian obsidian-tc: HITL confirmation bypass in tool execution (CVE-2026-115477)</title><link>https://feed.craftedsignal.io/briefs/2026-10-obsidian-tc-hitl-bypass/</link><pubDate>Fri, 23 Oct 2026 21:49:02 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-obsidian-tc-hitl-bypass/</guid><description>A vulnerability in the obsidian-tc server allows malicious or non-compliant clients to execute destructive tool calls by echoing validly bound request states even after a human-in-the-loop confirmation is declined.</description><content:encoded><![CDATA[<p>A vulnerability (CVE-2026-115477) exists in the obsidian-tc server component (v1.13.0 through v1.31.3) where the server fails to properly validate human-in-the-loop (HITL) confirmation responses. When a client performs a dispatch-gated tool call, the server issues an <code>inputRequired</code> confirmation challenge. Due to a flaw in the validation logic, the server trusts the echoed <code>requestState</code> provided by the client upon resubmission as proof of approval, even if the user previously declined the action. A malicious or non-compliant client can echo this state to bypass the user's explicit refusal, allowing destructive operations such as file deletion, cross-folder moves, and frontmatter replacements.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows for unauthorized execution of destructive vault operations that a user explicitly declined. The impact is limited to dispatch-gated tools configured with <code>destructive: true</code> or HITL floor scopes. The server cannot verify if a client actually rendered the form to the human, meaning an attacker-controlled client can simply provide an approval response regardless of human input.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Patch obsidian-tc to version 1.31.4 or later immediately.</li>
<li>For environments unable to patch, transition to stdio-based deployments or unset <code>auth.jwtSecret</code> to force usage of the legacy CLI-based <code>elicit_token</code> mechanism.</li>
<li>Audit logs for suspicious tool call patterns where a rejection is followed by an immediate resubmission from the same client session.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>hitl-bypass</category><category>obsidian-tc</category></item></channel></rss>