High 7.1Published Oct 23, 2026

CVE-2026-115478obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes

Updated under an hour ago (Oct 28, 2026, 10:40 AM ET)

Does this affect you?

It affects The-40-Thieves obsidian-tc. Add what you run to find out whether that includes you.

EPSS puts the chance of exploitation in the next 30 days at 0.32%, higher than 25% of scored CVEs.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for The-40-Thieves obsidian-tc

Exploited in the last 30 days

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.

CVSS: 7.1 HIGH (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
Weakness (CWE): CWE-459, CWE-863
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): 0.32% (percentile 25)
Assigned by: GitHub_M
NVD analysis: Deferred
Record last updated: Oct 23, 2026
First seen by InfoSec Signals: Oct 23, 2026

Affected products

Affected products

The-40-Thieves obsidian-tc 40_thieves:obsidian_tc (from the name)	from 1.0.1, < 1.31.4	CNA record

References

References

https://github.com/The-40-Thieves/obsidian-tc/security/advisories/GHSA-r3g7-r4hr-m258	x-refsource-confirm
https://github.com/The-40-Thieves/obsidian-tc/pull/978	x-refsource-misc
https://github.com/The-40-Thieves/obsidian-tc/commit/99f7914ca0fbeed92e7c4d39cc8c3e5830dab133	x-refsource-misc
https://github.com/The-40-Thieves/obsidian-tc/blob/v1.31.4/CHANGELOG.md	x-refsource-misc
https://github.com/The-40-Thieves/obsidian-tc/releases/tag/v1.31.4	x-refsource-misc

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.