{"vulnerability": "GHSA-6GQW-JQV7-V88M", "sightings": [{"uuid": "8505e689-f58d-4aea-956a-f84ffacb2ad7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-6GQW-JQV7-V88M", "type": "seen", "source": "https://gist.github.com/alon710/25e5cb1eacfa8b15e8ccfc6978e0021b", "content": "# GHSA-6GQW-JQV7-V88M: GHSA-6GQW-JQV7-V88M: Multi-Tenant Isolation Bypass in stigmem-node via Missing SQL Tenant Predicates\n\n> **CVSS Score:** 7.2\n> **Published:** 2026-06-19\n> **Full Report:** https://cvereports.com/reports/GHSA-6GQW-JQV7-V88M\n\n## Summary\nA critical vulnerability exists in the stigmem-node package when running the opt-in stigmem-plugin-multi-tenant plugin. Due to a failure to enforce tenant-scoping filters on database queries within the decay sweep, quarantine moderation, and right-to-be-forgotten (RTBF) subsystems, an authorized caller belonging to one tenant can access, modify, and delete facts belonging to all other tenants. This broken object level authorization (BOLA) vulnerability allows cross-tenant data manipulation and information leakage.\n\n## TL;DR\nA multi-tenant isolation bypass in stigmem-node allows authenticated users of one tenant to read, modify, and delete data belonging to all other tenants due to a lack of SQL tenant_id filters in the decay, quarantine, and tombstone systems.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-863 (Incorrect Authorization)\n- **Attack Vector**: Network (AV:N)\n- **CVSS v4.0 Score**: 7.2 (High)\n- **Impact**: High (Integrity and Availability Compromise)\n- **Exploit Status**: Proof-of-Concept\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- stigmem-node running stigmem-plugin-multi-tenant\n- **stigmem-node**: < 0.9.0a12 (Fixed in: `0.9.0a12`)\n\n## Mitigation\n\n- Upgrade to stigmem-node version 0.9.0a12 or later.\n- Set STIGMEM_MULTI_TENANT_ENABLED to false if multi-tenancy is not required.\n- Implement egress and access filters at the WAF level on decay and quarantine API routes.\n\n**Remediation Steps:**\n1. Check the current running version of the stigmem-node package.\n2. Update requirements.txt or dependency lockfiles to target >=0.9.0a12.\n3. Restart the stigmem-node service to apply the code modifications.\n4. Validate database records to ensure no unauthorized expiration overrides have been written by external tenants.\n\n## References\n\n- [GHSA-6GQW-JQV7-V88M Security Advisory](https://github.com/advisories/GHSA-6GQW-JQV7-V88M)\n- [Pull Request #728: Fix tenant-scoping in decay, quarantine, and tombstones](https://github.com/eidetic-labs/stigmem/pull/728)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/GHSA-6GQW-JQV7-V88M) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-06-22T05:42:09.000000Z"}]}