GHSA-6gqw-jqv7-v88m: stigmem-node: decay sweep expires and counts facts across all tenants (cross-tenant BOLA)
Summary On a multi-tenant stigmem node, a caller holding a write credential for one tenant can run a decay sweep that acts on every tenant's facts. The candidate-selection queries in lifecycle/decay.py (selectttlcandidates, selectconfidencecandidates) carried no tenantid predicate, and the caller's tenant was not threaded into the sweep or its async worker (rundecaysweep / decayjobworker), reached via POST…
Published Jun 19, 2026
Affected packages
stigmem-node
- Ecosystem
- PyPI
- Affected
- < 0.9.0a12
- Fixed in
- 0.9.0a12
- Check
pip show stigmem-node
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
On a multi-tenant stigmem node, a caller holding a write credential for one tenant can run a decay sweep that acts on every tenant's facts. The candidate-selection queries in lifecycle/decay.py (_select_ttl_candidates, _select_confidence_candidates) carried no tenant_id predicate, and the caller's tenant was not threaded into the sweep or its async worker (run_decay_sweep / _decay_job_worker), reached via POST /v1/decay/sweep.
Impact
A sweep with ttl_seconds=0 expires all tenants' facts — cross-tenant data destruction (integrity and availability). A dry_run sweep returns a global candidate count, acting as a cross-tenant existence/volume oracle (information disclosure).
Affected configurations
This is a cross-tenant break. It is exploitable only on deployments running the opt-in stigmem-plugin-multi-tenant (multiple tenants on one node). A default single-tenant node has only tenant="default" — there is no second tenant to cross — so it is not exploitable on default deployments. The rating is HIGH for the multi-tenant deployments the plugin exists to isolate.
Patches
Fixed in 0.9.0a12 (PR #728): identity.tenant_id is threaded into run_decay_sweep and _decay_job_worker, and AND tenant_id = ? was added to the candidate selectors and the graph-sync. A tenant-B sweep now leaves tenant-A facts untouched, and dry_run counts only the caller's tenant. The check_fact_query_tenant_scope.py CI guard was extended to scan lifecycle/ so this class cannot silently regress.
Workarounds
None other than upgrading to 0.9.0a12. Single-tenant deployments are unaffected.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesGHSA-5p3m-vhh6-9236
stigmem-node has blind SSRF via unvalidated webhook subscription delivery_address
medium6.3Aug 20, 2026GHSA-x26h-xmv8-gxf7
stigmem-node: RTBF tombstones are mis-attributed and suppress reads tenant-blind (cross-tenant BOLA)
high7.2Jun 19, 2026GHSA-xhv3-q4xx-349r
stistigmem-node: quarantine review surface exposes and mutates other tenants' quarantined facts (cross-tenant BOLA)
high8.6Jun 19, 2026GHSA-9pc9-4crj-mhpj
stigmem-node's Postgres schema identifier handling required defensive quoting
high7.5May 29, 2026GHSA-9vp8-3hmv-8fgh
stigmem-node's federation peer registration lacked explicit out-of-band approval
critical9.1May 29, 2026GHSA-fp6w-8wpg-74g5
stigmem-node: Auth-disabled deployments may grant broad anonymous access outside loopback
critical9.2May 29, 2026
