CVE-2026-115477: CWE-285: Improper Authorization in The-40-Thieves obsidian-tc
Description
obsidian-tc versions from 1.13.0 up to but not including 1.31.4 contain an improper authorization vulnerability. This flaw allows a client to bypass human approval for certain destructive vault operations when using Streamable HTTP deployment with auth.jwtSecret configured and a client supporting elicitation.form. The server incorrectly trusts a previously minted requestState as proof of approval, enabling execution of dispatch-gated destructive actions without explicit human consent. The issue is fixed in version 1.31.4.
CVSS v4.0
Score 7.1high
Affected software
The-40-Thieves
obsidian-tc
pkg:github/the-40-thieves/obsidian-tcRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in obsidian-tc (versions >=1.13.0 <1.31.4) arises from improper authorization related to the elicitation form approval process in a Streamable HTTP deployment with auth.jwtSecret configured. A client that supports elicitation.form can resubmit a call with a valid requestState minted before the elicitation leg was requested, causing the server to trust this state as approval even if the human declined or omitted the response. This allows execution of dispatch-gated destructive vault operations without human approval, although the client still requires ordinary tool permissions. The vulnerability does not affect stdio deployments or those without auth.jwtSecret set. The issue is resolved in version 1.31.4.
Potential Impact
An attacker or a misbehaving client can bypass the human-in-the-loop approval process for destructive vault operations, potentially leading to unauthorized destructive changes such as overwriting or moving notes. The attacker must have the necessary tool permissions but can execute these operations without explicit human consent, increasing the risk of unauthorized data modification or loss.
Mitigation Recommendations
Upgrade obsidian-tc to version 1.31.4 or later, where this improper authorization vulnerability is fixed. Deployments using stdio or without auth.jwtSecret configured are not affected by this issue. No other mitigations are indicated, and the fix does not prevent a malicious client from fabricating approval, but it ensures the server no longer trusts stale requestState values as proof of human approval.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-22T15:06:52.738Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6adb6fb44d27ba8daa33ac33
Added to database: 10/23/2026, 14:31:16 UTC
Last enriched: 10/23/2026, 14:45:43 UTC
Last updated: 10/23/2026, 15:26:05 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.