This vulnerability in the Obsidian Context Protocol server, observed in obsidian‑tc versions 1.0.1 through 1.31.4, is caused by the memory‑lifecycle tools regenerating SQLite‑backed memory notes without properly preserving note ownership or handling failed operations. As a result, an authorized user with memory‑tool permissions can cause an unowned note to have its entire body overwritten or, during a partial lifecycle operation, leave the operating system’s SQLite file and the on‑disk memory graph out of sync. The impact is a loss or corruption of vault content, leading to integrity compromise of the note set and potential loss of business‑critical data.

The vulnerability is specific to The‑40‑Thieves’ obsidian‑tc product. All releases from version 1.0.1 up to, but not including, 1.31.4 are affected. The software is a governed, agent‑ready Model Context Protocol server used by Obsidian vaults.

The CVSS score of 7.1 classifies the flaw as high severity. The EPSS score is not available, and the vulnerability is not yet listed in CISA’s KEV catalog. Exploitation requires an attacker to possess authorized memory‑tool permissions within the vault; it does not bypass deletion confirmation and does not exploit external network interfaces. The main attack vector is likely internal or from a compromised account that can invoke the memory‑lifecycle API. If such a user exists, they could unintentionally or intentionally cause data loss and incomplete lifecycle operations, undermining trust in the vault’s content.