{"id":"CVE-2026-76238","aliases":["GHSA-6gqw-jqv7-v88m"],"title":"stigmem-node: decay sweep expires and counts facts across all tenants (cross-tenant BOLA)","summary":"stigmem-node: decay sweep expires and counts facts across all tenants (cross-tenant BOLA)","severity":"high","vendor":"stigmem-node","product":"stigmem-node","ecosystem":"pip","affected":["stigmem-node < 0.9.0a12"],"patched":["stigmem-node 0.9.0a12"],"published":"2026-06-19","updated":"2026-08-20","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-6gqw-jqv7-v88m","references":[{"url":"https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-6gqw-jqv7-v88m"},{"url":"https://github.com/eidetic-labs/stigmem/pull/728"},{"url":"https://github.com/eidetic-labs/stigmem"}],"tags":["osv","pip"],"epss":0.00265,"epssPercentile":0.18706,"ingestedAt":"2026-08-20T19:23:05.202Z","slug":"CVE-2026-76238","body":"## Overview\n\n### Summary\nOn 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`.\n\n### Impact\nA 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).\n\n### Affected configurations\nThis 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.\n\n### Patches\nFixed 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.\n\n### Workarounds\nNone other than upgrading to `0.9.0a12`. Single-tenant deployments are unaffected.\n\n## Affected packages\n\n- `stigmem-node < 0.9.0a12`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `stigmem-node 0.9.0a12`","depth":"twilight","depthScore":41,"depthScoreParts":{"impact":41.3,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}