CVE-2026-115478: CWE-459: Incomplete Cleanup in The-40-Thieves obsidian-tc
Description
obsidian-tc versions from 1.0.1 up to but not including 1.31.4 have an incomplete cleanup vulnerability where certain entity lifecycle operations can overwrite or corrupt vault notes due to inconsistent handling of note ownership and filesystem failures. This can result in unauthorized overwriting of note bodies and inconsistencies between the SQLite memory graph and notes on disk. 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
obsidian-tc is a Model Context Protocol server for Obsidian vaults. Versions 1.0.1 through 1.31.3 have a vulnerability involving incomplete cleanup during entity lifecycle operations such as create_entity, link_entities, rename_entity, unlink_entities, and delete_entity. These operations regenerate memory notes from SQLite at computed paths but do not reliably preserve note ownership or handle failures consistently. This can cause overwriting of notes not owned by the entity being written, especially if note names sanitize to the same path. rename_entity can overwrite foreign notes without validating ownership. Additionally, several operations mutate SQLite before filesystem changes, so a filesystem failure can leave the memory graph inconsistent with on-disk notes. Authorized callers with memory-tool permissions can unintentionally destroy note bodies outside their entity scope. delete_entity requires additional deletion permissions and confirmation, so it is less affected. Snapshot-before-write via restore_note mitigates overwrites only if snapshots are enabled and the note was previously written through obsidian-tc. The vulnerability is fixed in version 1.31.4.
Potential Impact
An authorized user with memory-tool permissions can unintentionally overwrite or destroy the content of vault notes outside the intended entity due to inconsistent ownership validation and incomplete cleanup during entity lifecycle operations. This can lead to data loss or corruption within the Obsidian vault. The vulnerability does not bypass delete_entity's additional deletion permissions and confirmation requirements. The memory graph and on-disk notes can become inconsistent after certain failures, potentially impacting data integrity.
Mitigation Recommendations
Upgrade obsidian-tc to version 1.31.4 or later, where this vulnerability is fixed. If upgrading is not immediately possible, enable snapshot-before-write functionality via restore_note to mitigate overwrites, noting this only protects notes previously written through obsidian-tc and when snapshots are enabled. No other specific mitigations are indicated. Patch status is confirmed fixed in 1.31.4.
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: 6adb6fb44d27ba8daa33ac34
Added to database: 10/23/2026, 14:31:16 UTC
Last enriched: 10/23/2026, 14:45:40 UTC
Last updated: 10/23/2026, 15:26:05 UTC
Views: 3
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.