GHSA-xhv3-q4xx-349r: stistigmem-node: quarantine review surface exposes and mutates other tenants' quarantined facts (cross-tenant BOLA)
Summary On a multi-tenant stigmem node, a tenant administrator could list, read, and admit or reject quarantined facts belonging to other tenants. The list/count queries and getquarantinedfact in routes/quarantine.py lacked an f.tenantid = identity.tenantid predicate, and the garden lookup was not tenant-scoped — reached via the /v1/quarantine list and admit/reject endpoints.
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 tenant administrator could list, read, and admit or reject quarantined facts belonging to other tenants. The list/count queries and _get_quarantined_fact in routes/quarantine.py lacked an f.tenant_id = identity.tenant_id predicate, and the garden lookup was not tenant-scoped — reached via the /v1/quarantine list and admit/reject endpoints.
Impact
Cross-tenant confidentiality (reading another tenant's quarantined content) and cross-tenant integrity (moderating — admitting or rejecting — another tenant's facts), gated only by a plain tenant write capability rather than a node-level admin authority.
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): AND f.tenant_id = identity.tenant_id was added to the list/count queries and _get_quarantined_fact; the garden lookup is now tenant-scoped; and any genuinely cross-tenant moderation is gated behind can_admin_federation() (node superadmin), not a tenant write capability. A tenant-B admin can no longer list, admit, or reject tenant-A's quarantined facts.
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-6gqw-jqv7-v88m
stigmem-node: decay sweep expires and counts facts across all tenants (cross-tenant BOLA)
high7.2Jun 19, 2026GHSA-x26h-xmv8-gxf7
stigmem-node: RTBF tombstones are mis-attributed and suppress reads tenant-blind (cross-tenant BOLA)
high7.2Jun 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
