obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes
### Summary `create_entity`, `link_entities`, `rename_entity`, `unlink_entities` and `delete_entity` regenerate a memory note's body from SQLite at the computed `memory//.md` path. When a note already existed at that path and was not owned by the entity being written (a hand-authored note, or an orphan left by a different entity whose name sanitized to the same path), its entire body was overwritten on the next write naming that `(type, name)`, keeping only its frontmatter. Separately, several of these tools inserted or removed their SQLite row before the fallible filesystem step, so a refused note write could leave a relation gone, a retired status committed, or the wrong entity deleted. ### Details - `create_entity` and `link_entities` inserted the SQL row or relation before materialization. - `rename_entity` seeded the destination path with a direct atomic write that bypassed the ownership check, and for a status-only rename could commit a retired status with the note write refused. - `unlink_entities` removed the relation row before discovering the source note's rematerialization would be refused. - `delete_entity`'s cascade could delete the target and its relations before a neighbour's note was found to be foreign. The overwrite exists in every released version since `materializeEntity` shipped (`git show v1.0.1:packages/server/src/memory/materialize.ts`). ### Impact An authorized caller with memory-write scope (any agent using the M5 memory tools) can, without intending
- Products
- obsidian-tc
- Affected versions
- Not specified
- Fixed versions
- 1.31.4
- CVEs
- CVE-2026-115478
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 02:32 UTC · Revision 1
Source evidence
obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes
core-osv · Original sourcePublished 23 Oct 2026, 18:47 UTC
### Summary `create_entity`, `link_entities`, `rename_entity`, `unlink_entities` and `delete_entity` regenerate a memory note's body from SQLite at the computed `memory//.md` path. When a note already existed at that path and was not owned by the entity being written (a hand-authored note, or an orphan left by a different entity whose name sanitized to the same path), its entire body was overwritten on the next write naming that `(type, name)`, keeping only its frontmatter. Separately, several of these tools inserted or removed their SQLite row before the fallible filesystem step, so a refused note write could leave a relation gone, a retired status committed, or the wrong entity deleted. ### Details - `create_entity` and `link_entities` inserted the SQL row or relation before materialization. - `rename_entity` seeded the destination path with a direct atomic write that bypassed the ownership check, and for a status-only rename could commit a retired status with the note write refused. - `unlink_entities` removed the relation row before discovering the source note's rematerialization would be refused. - `delete_entity`'s cascade could delete the target and its relations before a neighbour's note was found to be foreign. The overwrite exists in every released version since `materializeEntity` shipped (`git show v1.0.1:packages/server/src/memory/materialize.ts`). ### Impact An authorized caller with memory-write scope (any agent using the M5 memory tools) can, without intending
osv:GHSA-r3g7-r4hr-m258
obsidian-tc
Fixed versions: 1.31.4
Complete source record
{
"id": "7947a05d957666c246d6da00c135b1dadf81410f32d8275e81ef8b85fa1518a6",
"url": "https://osv.dev/vulnerability/GHSA-r3g7-r4hr-m258",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes",
"summary": "### Summary `create_entity`, `link_entities`, `rename_entity`, `unlink_entities` and `delete_entity` regenerate a memory note's body from SQLite at the computed `memory//.md` path. When a note already existed at that path and was not owned by the entity being written (a hand-authored note, or an orphan left by a different entity whose name sanitized to the same path), its entire body was overwritten on the next write naming that `(type, name)`, keeping only its frontmatter. Separately, several of these tools inserted or removed their SQLite row before the fallible filesystem step, so a refused note write could leave a relation gone, a retired status committed, or the wrong entity deleted. ### Details - `create_entity` and `link_entities` inserted the SQL row or relation before materialization. - `rename_entity` seeded the destination path with a direct atomic write that bypassed the ownership check, and for a status-only rename could commit a retired status with the note write refused. - `unlink_entities` removed the relation row before discovering the source note's rematerialization would be refused. - `delete_entity`'s cascade could delete the target and its relations before a neighbour's note was found to be foreign. The overwrite exists in every released version since `materializeEntity` shipped (`git show v1.0.1:packages/server/src/memory/materialize.ts`). ### Impact An authorized caller with memory-write scope (any agent using the M5 memory tools) can, without intending",
"evidence": "osv:GHSA-r3g7-r4hr-m258",
"products": [
{
"name": {
"value": "obsidian-tc",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.31.4",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "GHSA-r3g7-r4hr-m258",
"aliases": [
"CVE-2026-115478",
"GHSA-r3g7-r4hr-m258"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "1.0.1"
},
{
"fixed": "1.31.4"
}
]
}
],
"package": {
"name": "obsidian-tc",
"purl": "pkg:npm/obsidian-tc",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-r3g7-r4hr-m258/GHSA-r3g7-r4hr-m258.json",
"last_known_affected_version_range": "<= 1.31.3"
}
}
],
"modified": "2026-10-23T19:00:40.500298795Z",
"provider": "osv",
"references": [
"https://github.com/The-40-Thieves/obsidian-tc/security/advisories/GHSA-r3g7-r4hr-m258",
"https://nvd.nist.gov/vuln/detail/CVE-2026-115478",
"https://github.com/The-40-Thieves/obsidian-tc/pull/978",
"https://github.com/The-40-Thieves/obsidian-tc/commit/99f7914ca0fbeed92e7c4d39cc8c3e5830dab133",
"https://github.com/The-40-Thieves/obsidian-tc",
"https://github.com/The-40-Thieves/obsidian-tc/blob/v1.31.4/CHANGELOG.md",
"https://github.com/The-40-Thieves/obsidian-tc/releases/tag/v1.31.4"
],
"provider_metadata": {
"cwe_ids": [
"CWE-459",
"CWE-863"
],
"severity": "HIGH",
"github_reviewed": true,
"nvd_published_at": "2026-10-23T15:17:30Z",
"github_reviewed_at": "2026-10-23T18:47:25Z"
}
},
"related_cves": [
{
"value": "CVE-2026-115478",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 424613,
"published_at": "2026-10-23T18:47:25+00:00"
}