Executive brief
A vulnerability in the stigmem-node software allows a user with access to one organization's data (tenant) to trigger maintenance tasks that affect all other organizations on the same server. This can lead to the unauthorized deletion of data across the entire platform or allow an attacker to gather information about the volume of data held by other customers. This issue only affects systems specifically configured for multi-tenancy using the optional multi-tenant plugin.
Technical details
A Broken Object Level Authorization (BOLA) vulnerability exists in stigmem-node's decay sweep implementation within `lifecycle/decay.py`. The functions `_select_ttl_candidates` and `_select_confidence_candidates` failed to include a `tenant_id` predicate in their database queries. Consequently, when a user triggers a sweep via `POST /v1/decay/sweep`, the process acts globally rather than being restricted to the caller's tenant. An attacker with 'write' credentials for a single tenant can cause cross-tenant data destruction by setting `ttl_seconds=0` or perform information disclosure regarding other tenants' data volumes using the `dry_run` flag. This is only exploitable on deployments using `stigmem-plugin-multi-tenant`. The issue is fixed in version 0.9.0a12 by threading `identity.tenant_id` through the decay job worker and enforcing tenant scoping in SQL queries.
Affected products
- eidetic-labs stigmem-node < 0.9.0a12
Timeline
- 2026-06-13: patched: PR #728 merged into main
- 2026-06-19: disclosed: GitHub Advisory published