Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes

CVE-2026-115478GHSA-r3g7-r4hr-m258

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (obsidian-tc 1.31.4), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm obsidian-tc

    Affected
    >= 1.0.1, <= 1.31.3
    Fixed in
    1.31.4

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.1 · 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 source
EPSS
  • CVE-2026-115478: 0.32% estimated exploitation activity in the next 30 days; percentile 25.43 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary createentity, linkentities, renameentity, unlinkentities and deleteentity regenerate a memory note's body from SQLite at the computed memory/<type/<name.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 - createentity and linkentities inserted the SQL row or relation before materialization. - renameentity 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. - unlinkentities…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 5 · amended ·

    Amended from ghsa record GHSA-r3g7-r4hr-m258

  2. Revision 4 · amended ·

    Amended from ghsa record GHSA-r3g7-r4hr-m258

  3. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  4. Revision 2 · amended ·

    Amended from osv record GHSA-r3g7-r4hr-m258

  5. Revision 1 · created ·

    Published from ghsa record GHSA-r3g7-r4hr-m258

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-115478

Advisory: obsidian-tc: Memory-lifecycle tools overwrite unowned notes or partially commit lifecycle changes
IDs: CVE-2026-115478, GHSA-r3g7-r4hr-m258
Record: https://patchnext.com/advisories/cve-2026-115478 (revision 5, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: obsidian-tc 1.31.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm obsidian-tc: affected >= 1.0.1, <= 1.31.3; fixed in 1.31.4

## Suggested inspection (read-only)
- `npm ls obsidian-tc --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on obsidian-tc.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r3g7-r4hr-m258 (GitHub-reviewed advisory GHSA-r3g7-r4hr-m258 lists affected ranges: npm obsidian-tc >=1.0.1 <=1.31.3)
- Verified: https://osv.dev/vulnerability/GHSA-r3g7-r4hr-m258 (OSV record GHSA-r3g7-r4hr-m258 lists affected ranges: npm obsidian-tc >=1.0.1 <1.31.4 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…