Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The npm package obsidian-tc, versions from 1.0.1 before 1.31.4, can overwrite the body of an existing vault note that the entity being written does not own, and can leave relations, statuses, or entities changed in SQLite when the note write is refused. An authorized caller with memory-write scope can trigger this through the memory lifecycle tools, with the note body lost except for its frontmatter. Upgrade to version 1.31.4, which refuses writes over notes not owned by the entity and runs an ownership check before any database change.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.1 | High | 4.0 | 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 | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0032, the 25th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 13:33 UTC First seen by agentprime
- 31 Oct 2026, 13:33 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-r3g7-r4hr-m258
- OSV: GHSA-r3g7-r4hr-m258
- github.com/The-40-Thieves/obsidian-tc/security/advisories/GHSA-r3g7-r4hr-m258
- nvd.nist.gov/vuln/detail/CVE-2026-115478
- github.com/The-40-Thieves/obsidian-tc/pull/978
- github.com/The-40-Thieves/obsidian-tc/commit/99f7914ca0fbeed92e7c4d39cc8c3e5830dab133
- github.com/The-40-Thieves/obsidian-tc
- github.com/The-40-Thieves/obsidian-tc/blob/v1.31.4/CHANGELOG.md
- github.com/The-40-Thieves/obsidian-tc/releases/tag/v1.31.4