Description
stigmem-node before 0.9.0a12 contains a broken object level authorization (cross-tenant BOLA) vulnerability in the quarantine review endpoints. On multi-tenant deployments running the opt-in stigmem-plugin-multi-tenant, the list/count queries and _get_quarantined_fact in routes/quarantine.py lacked a tenant_id predicate and the garden lookup was not tenant-scoped, allowing a tenant administrator with only a plain tenant write capability to list, read, and admit or reject quarantined facts belonging to other tenants via the /v1/quarantine endpoints. Default single-tenant deployments are not affected.
Published: 2026-08-19
Score: 8.6 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The affected component lacks proper tenant scoping for quarantine review endpoints, allowing a tenant administrator with only write privileges to list, read, and admit or reject quarantined facts from other tenants. This broken object‑level authorization results in unauthorized disclosure and manipulation of sensitive data belonging to other tenants, potentially compromising their quarantine decisions.

Affected Systems

The flaw exists in stigmem-node prior to version 0.9.0a12 when the stigmem-plugin-multi‑tenant is enabled in a multi‑tenant deployment. Default single‑tenant installations are not affected.

Risk and Exploitability

With a CVSS score of 8.6 and no publicly available exploit probability data, the vulnerability poses a high risk to organizations running multi‑tenant deployments. An attacker must possess tenant‑level administrative credentials (a role normally available to legitimate tenant administrators) and then target the /v1/quarantine endpoints to retrieve or alter other tenants’ quarantine data. Because the attack requires authentication and is limited to tenant‑admin scope, impact is confined to tenants whose administrators are compromised or misused, but the breadth of data exposed can be significant. The vulnerability is not currently listed in the CISA KEV catalog.

Generated by OpenCVE AI on August 19, 2026 at 18:57 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade stigmem-node to version 0.9.0a12 or later.
  • If the multi‑tenant plugin is not required, disable or uninstall stigmem-plugin-multi‑tenant.
  • Configure your deployment to enforce tenant isolation and limit the use of tenant admin privileges within each tenant.

Generated by OpenCVE AI on August 19, 2026 at 18:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 19 Aug 2026 14:15:00 +0000

Type Values Removed Values Added
Description stigmem-node before 0.9.0a12 contains a broken object level authorization (cross-tenant BOLA) vulnerability in the quarantine review endpoints. On multi-tenant deployments running the opt-in stigmem-plugin-multi-tenant, the list/count queries and _get_quarantined_fact in routes/quarantine.py lacked a tenant_id predicate and the garden lookup was not tenant-scoped, allowing a tenant administrator with only a plain tenant write capability to list, read, and admit or reject quarantined facts belonging to other tenants via the /v1/quarantine endpoints. Default single-tenant deployments are not affected.
Title stigmem before 0.9.0a12 Cross-Tenant BOLA via quarantine
Weaknesses CWE-639
References
Metrics cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-19T14:02:15.899Z

Reserved: 2026-08-19T11:38:33.224Z

Link: CVE-2026-76237

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-19T14:17:55.840

Modified: 2026-08-19T14:17:55.840

Link: CVE-2026-76237

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-19T19:00:05Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key