ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-115477

obsidian-tc: Declined human-in-the-loop confirmations can permit destructive calls over HTTP

Published Oct 23, 2026 · catalog updated Oct 23, 2026 · The-40-Thieves

Last checked Oct 25, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-115477. EPSS is 0.35%. Act only if a listed version of The-40-Thieves is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.35%
Remediation
Version ranges on file
Affected products
npm obsidian-tc · vendor The-40-Thieves obsidian-tc

### Summary On a Streamable HTTP deployment with configured, serving a 2026-07-28-era client that declared support, a call to a dispatch-gated tool ( , or a scope with an HITL floor) that was offered an confirmation could still complete after the human declined, cancelled, or the elicitation response was omitted or malformed, provided the client echoed the validly bound on resubmission. The server trusted an authentic, call-bound state as proof of approval; the state is minted before the elicitation leg is asked, so it proves only that the resubmission belongs to the same call. ### Details Reproduced directly: a tool call, offered , answered with on the leg, still wrote. Present since the 2026-07-28 round trip shipped in v1.13.0 (THE-583). Only dispatch-gated tools were reachable; the sixteen handler-side conditionally gated tools ( overwrite, , and others) did not read the elicitation state on the modern wire at all, so they neither let a decline nor an approval through. ### Impact A client that echoes state after a decline can execute destructive vault operations (delete, cross-folder move, frontmatter replace, link rewrite) that the human explicitly refused. The precondition is a compliant client behaving incorrectly or a client under an attacker's control; the human's refusal is not enforced by the server. ### Patches Fixed in 1.31.4: the server now also requires the confirm leg's own response ( ) to be before trusting the echoed state. A declined, cancelled or not-approved round renders the ordinary error and is never offered a second round for the same declined confirmation. The same release adds server-initiated in-band confirmation on stdio (legacy era), so stdio agents no longer need to mint themselves. ### Not addressed A malicious or non-compliant client can still answer its own leg with an approval regardless of what the human said. The server cannot verify that the client rendered the form or that a human saw it; this is inherent to the client-driven ha

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm obsidian-tc1.13.0 → 1.31.4
  • npm obsidian-tc>= 1.13.0, <= 1.31.3
  • vendor The-40-Thieves obsidian-tcversion unspecified

How to fix CVE-2026-115477

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-115477. EPSS is 0.35%. Act only if a listed version of The-40-Thieves is installed.

Which versions are affected?

Compare what you have installed with 1.13.0 → 1.31.4, >= 1.13.0, <= 1.31.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-285: Improper Authorization; CWE-863: Incorrect Authorization. EPSS 0.35%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 23, 2026 · GitHub Advisory Database

    Detected

    ### Summary On a Streamable HTTP deployment with configured, serving a 2026-07-28-era client that declared support, a call to a dispatch-gated tool ( , or a scope with an HITL floor) that was offered an confirmation could still complete after the human declined, cancelled, or the elicitation response was omitted or malformed, provided the client echoed the validly bound on resubmission. The server

  2. Oct 23, 2026 · GitHub Advisory Database

    Fix available

    obsidian-tc fixed in 1.31.4

  3. Oct 23, 2026 · GitHub Advisory Database

    Fix available

    obsidian-tc fixed in 1.31.4

  4. Oct 23, 2026 · GitHub Advisory Database

    Updated

    ### Summary On a Streamable HTTP deployment with configured, serving a 2026-07-28-era client that declared support, a call to a dispatch-gated tool ( , or a scope with an HITL floor) that was offered an confirmation could still complete after the human declined, cancelled, or the elicitation response was omitted or malformed, provided the client echoed the validly bound on resubmission. The server

Sources

  • CVE.orgVulnerability recordCVE-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 configured and a 2026-07-28-era client declaring support, a dispatch-gated tool call offered an confirmation could still comple

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-115477

    30-day exploitation probability 0.35%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-737x-cwfr-5vvc

    obsidian-tc: Declined human-in-the-loop confirmations can permit destructive calls over HTTP

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-115477

    On a Streamable HTTP deployment with auth.jwtSecret configured, serving a 2026-07-28-era client that declared elicitation.form support, a call to a dispatch-gated tool (destructive: true, or a scope with an HITL floor) that was offered an inputRequired confirmation could still complete after the human declined, cancelled, or the elicitation response was omitted or malformed, provided the client ec

    advisories.gitlab.com
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-737x-cwfr-5vvc

    obsidian-tc: Declined human-in-the-loop confirmations can permit destructive calls over HTTP

    osv.dev

References

Freshness

Last verified in this catalog Oct 25, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitLab Advisory DatabaseOct 25, 2026
  • FIRST EPSSOct 25, 2026
  • CVE.orgOct 23, 2026
  • GitHub Advisory DatabaseOct 23, 2026
  • OpenSSF OSV / OSV ScannerOct 23, 2026