{"cve":"CVE-2026-115478","nvd":{"published":"2026-10-23T15:17:30.023","modified":"2026-10-23T15:17:30.147","status":"Deferred","description":"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_v4":{"vector":"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","score":7.1},"cvss_v3":null,"cwes":["CWE-459","CWE-863"],"references":["https://github.com/The-40-Thieves/obsidian-tc/blob/v1.31.4/CHANGELOG.md","https://github.com/The-40-Thieves/obsidian-tc/commit/99f7914ca0fbeed92e7c4d39cc8c3e5830dab133","https://github.com/The-40-Thieves/obsidian-tc/pull/978","https://github.com/The-40-Thieves/obsidian-tc/releases/tag/v1.31.4","https://github.com/The-40-Thieves/obsidian-tc/security/advisories/GHSA-r3g7-r4hr-m258"],"products":[],"source":"nvd","synced_at":"2026-10-23T16:39:28.036610720+00:00"},"epss":{"cve":"CVE-2026-115478","score":0.00323,"percentile":0.25137,"date":"2026-10-25"},"kev":null,"osv":[{"id":"GHSA-r3g7-r4hr-m258","url":"https://osv.dev/vulnerability/GHSA-r3g7-r4hr-m258","summary":"obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes","modified":"2026-10-23T19:00:40.500298795Z","packages":[{"ecosystem":"npm","name":"obsidian-tc","purl":"pkg:npm/obsidian-tc","ranges":[">=1.0.1 <1.31.4"],"fixed":["1.31.4"]}]}],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}