Executive brief
A vulnerability in the stigmem-node software allows data deletion requests (tombstones) from one organization to affect another organization's data in multi-tenant environments. This means a user in one account could potentially hide or misattribute data belonging to a different account, compromising the integrity of the "right-to-be-forgotten" mechanism. This issue only affects systems specifically configured for multi-tenancy using the optional multi-tenant plugin.
Technical details
A cross-tenant BOLA vulnerability exists in stigmem-node when using the 'stigmem-plugin-multi-tenant' plugin. The vulnerability stems from two root causes: (1) the 'issue_tombstone' function defaulted to a 'default' tenant ID rather than the caller's specific ID, and (2) the read-suppression logic in 'routes/facts/common.py' and 'lifecycle/tombstones.py' lacked tenant_id predicates. An authenticated attacker in one tenant can issue tombstones that are applied globally or to the wrong tenant, effectively suppressing fact queries and provenance data for other tenants. This has been patched in version 0.9.0a12 by ensuring tenant_id is correctly propagated and enforced in all tombstone read/write paths.
Affected products
- eidetic-labs stigmem-node < 0.9.0a12
Timeline
- 2026-06-13: patched: Fix merged in PR #728
- 2026-06-19: advisory: GHSA-x26h-xmv8-gxf7 published