Summary
stistigmem-node: quarantine review surface exposes and mutates other tenants' quarantined facts (cross-tenant BOLA)
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.
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.
Workarounds
None other than upgrading to 0.9.0a12. Single-tenant deployments are unaffected.
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.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is GHSA-XHV3-Q4XX-349R? GHSA-XHV3-Q4XX-349R is a high-severity incorrect authorization vulnerability in stigmem-node (pip), affecting versions < 0.9.0a12. It is fixed in 0.9.0a12. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- Which versions of stigmem-node are affected by GHSA-XHV3-Q4XX-349R? stigmem-node (pip) versions < 0.9.0a12 is affected.
- Is there a fix for GHSA-XHV3-Q4XX-349R? Yes. GHSA-XHV3-Q4XX-349R is fixed in 0.9.0a12. Upgrade to this version or later.
- Is GHSA-XHV3-Q4XX-349R exploitable, and should I be worried? Whether GHSA-XHV3-Q4XX-349R is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-XHV3-Q4XX-349R is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-XHV3-Q4XX-349R? Upgrade
stigmem-nodeto 0.9.0a12 or later.