CVE-2026-115478

Source
https://cve.org/CVERecord?id=CVE-2026-115478
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-115478.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-115478
Aliases
Published
2026-10-23T14:06:28Z
Modified
2026-11-17T07:00:57Z
Severity
  • 7.1 (High) CVSS_V4 - 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 CVSS Calculator
Summary
obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes
Details

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.

Database specific
{
    "cna_assigner":  "GitHub_M",
    "cwe_ids":  [
        "CWE-459",
        "CWE-863"
    ],
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/115xxx/CVE-2026-115478.json"
}
References

Affected packages

Git / github.com/The-40-Thieves/reliquary-tc

Affected ranges

Type
GIT
Repo
https://github.com/The-40-Thieves/reliquary-tc
Events
Database specific
Show details
{
    "extracted_events":  [
        {
            "range":  [
                {
                    "introduced":  "1.0.1"
                },
                {
                    "fixed":  "1.31.4"
                }
            ],
            "source":  "AFFECTED_FIELD",
            "strategy":  "StringRangeExpression"
        }
    ]
}

Affected versions

1.*
1.27.0
1.28.0
1.28.1
1.28.2
1.28.3
1.28.4
1.29.0
1.30.0
1.30.1
1.31.0
1.31.1
1.31.2
1.31.3
v1.*
v1.0.1
v1.0.2
v1.10.0
v1.11.0
v1.12.1
v1.13.0
v1.13.1
v1.14.0
v1.14.1
v1.14.2
v1.14.3
v1.15.0
v1.16.0
v1.17.0
v1.17.1
v1.18.0
v1.19.0
v1.2.1
v1.20.0
v1.21.0
v1.22.0
v1.23.0
v1.23.1
v1.23.2
v1.23.3
v1.23.4
v1.23.5
v1.23.6
v1.24.0
v1.25.0
v1.26.0
v1.27.0
v1.28.0
v1.28.1
v1.28.2
v1.28.3
v1.28.4
v1.29.0
v1.3.6
v1.30.0
v1.30.1
v1.31.0
v1.31.1
v1.31.2
v1.31.3
v1.4.0
v1.5.0
v1.6.0
v1.7.0
v1.8.0
v1.8.1
v1.9.0
v1.9.1

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-115478.json"