CVE-2026-115478: obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes
The-40-Thieves · obsidian-tc
Affected: The-40-Thieves obsidian-tc · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 25% of scored CVEs
DescriptionCVE.org
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. From 1.0.1 until 1.31.4, `create_entity`, `link_entities`, `rename_entity`, `unlink_entities` and `delete_entity` regenerate memory notes from SQLite at the computed `memory/<type>/<name>.md` path without reliably preserving note ownership or the consistency of a failed lifecycle operation. During shared materialization, a hand-authored note or an orphan left by a different entity whose name sanitized to the same path could have its entire body overwritten on the next write naming that type and name, with non-owned frontmatter preserved. `rename_entity` also seeded the destination path with a direct atomic write without validating ownership and could overwrite a foreign note there. Separately, several tools mutated SQLite before fallible filesystem work: `create_entity` and `link_entities` inserted the row or relation before materialization; `rename_entity` updated the entity, including a retired status, before updating its note; `unlink_entities` removed a relation before rematerializing the source note; and `delete_entity`'s cascade removed the target and its relations before rematerializing neighbouring notes. A later filesystem failure could therefore leave a row or relation changed and the memory graph inconsistent with the notes on disk even when the operation failed. An authorized caller with the required memory-tool permissions could, without intending to, destroy the body of a vault note outside the entity being written; `delete_entity` additionally requires its deletion permission and destructive confirmation, which this memory flaw does not bypass. Snapshots-before-write through `restore_note` mitigate the overwrite only where snapshots are enabled and the note had previously been written through obsidian-tc. This issue is fixed in version 1.31.4.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- The-40-Thieves · obsidian-tc>= 1.0.1, < 1.31.4
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- The-40-Thieves
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-115478 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-459cwe.mitre.org
- github.com/The-40-Thieves/obsidian-tc/security/advisories/GHSA-rgithub.com
- github.com/The-40-Thieves/obsidian-tc/pull/978github.com
- github.com/The-40-Thieves/obsidian-tc/commit/99f7914ca0fbeed92e7github.com
- github.com/The-40-Thieves/obsidian-tc/blob/v1.31.4/CHANGELOG.mdgithub.com
- github.com/The-40-Thieves/obsidian-tc/releases/tag/v1.31.4github.com