CVE-2026-76236: Authorization Bypass Through User-Controlled Key in eidetic-labs stigmem
stigmem-node before 0.9.0a12 contains a cross-tenant broken object level authorization (BOLA) flaw in the RTBF (right-to-be-forgotten) tombstone mechanism. issue_tombstone defaulted the tenant to "default" instead of the caller's tenant, allowing deletion records to be written to the wrong tenant, and the read-suppression path (_get_tombstone_filter and the tombstone scope cache) lacked a tenant_id predicate, so tombstone suppression was applied tenant-blind across fact queries and provenance reads. As a result, a tenant's deletion could be attributed to the wrong tenant and tombstone suppression could either hide facts belonging to other tenants or fail to hide facts within the correct tenant, undermining data isolation and RTBF guarantees. The issue is exploitable only on multi-tenant deployments running the opt-in stigmem-plugin-multi-tenant; single-tenant deployments are unaffected. Fixed in 0.9.0a12.
AI Analysis
Technical Summary
CVE-2026-76236 describes a cross-tenant broken object level authorization (BOLA) vulnerability in stigmem-node prior to 0.9.0a12. The flaw exists in the RTBF tombstone mechanism where the default tenant for deletion records was incorrectly set to "default" rather than the caller's tenant. Additionally, the read-suppression logic lacked tenant_id predicates, causing tombstone suppression to be applied tenant-blind across fact queries and provenance reads. This results in deletion records being misattributed to the wrong tenant and suppression either hiding facts from other tenants or failing to hide facts within the correct tenant. This vulnerability affects only multi-tenant deployments running the stigmem-plugin-multi-tenant and compromises data isolation and RTBF guarantees. The issue was fixed in version 0.9.0a12.
Potential Impact
The vulnerability allows unauthorized cross-tenant data access and deletion record misattribution in multi-tenant environments, undermining data isolation and the right-to-be-forgotten guarantees. This could lead to tenants seeing or hiding data incorrectly due to tenant-blind tombstone suppression. Single-tenant deployments are unaffected. There are no known exploits in the wild.
Mitigation Recommendations
A fix is available in stigmem-node version 0.9.0a12. Users running multi-tenant deployments with the stigmem-plugin-multi-tenant should upgrade to version 0.9.0a12 or later to remediate this vulnerability. Patch status is not explicitly confirmed beyond the stated fix version; verify with the vendor advisory for current remediation guidance.
CVE-2026-76236: Authorization Bypass Through User-Controlled Key in eidetic-labs stigmem
Description
stigmem-node before 0.9.0a12 contains a cross-tenant broken object level authorization (BOLA) flaw in the RTBF (right-to-be-forgotten) tombstone mechanism. issue_tombstone defaulted the tenant to "default" instead of the caller's tenant, allowing deletion records to be written to the wrong tenant, and the read-suppression path (_get_tombstone_filter and the tombstone scope cache) lacked a tenant_id predicate, so tombstone suppression was applied tenant-blind across fact queries and provenance reads. As a result, a tenant's deletion could be attributed to the wrong tenant and tombstone suppression could either hide facts belonging to other tenants or fail to hide facts within the correct tenant, undermining data isolation and RTBF guarantees. The issue is exploitable only on multi-tenant deployments running the opt-in stigmem-plugin-multi-tenant; single-tenant deployments are unaffected. Fixed in 0.9.0a12.
CVSS v4.0
Score 7.2high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-76236 describes a cross-tenant broken object level authorization (BOLA) vulnerability in stigmem-node prior to 0.9.0a12. The flaw exists in the RTBF tombstone mechanism where the default tenant for deletion records was incorrectly set to "default" rather than the caller's tenant. Additionally, the read-suppression logic lacked tenant_id predicates, causing tombstone suppression to be applied tenant-blind across fact queries and provenance reads. This results in deletion records being misattributed to the wrong tenant and suppression either hiding facts from other tenants or failing to hide facts within the correct tenant. This vulnerability affects only multi-tenant deployments running the stigmem-plugin-multi-tenant and compromises data isolation and RTBF guarantees. The issue was fixed in version 0.9.0a12.
Potential Impact
The vulnerability allows unauthorized cross-tenant data access and deletion record misattribution in multi-tenant environments, undermining data isolation and the right-to-be-forgotten guarantees. This could lead to tenants seeing or hiding data incorrectly due to tenant-blind tombstone suppression. Single-tenant deployments are unaffected. There are no known exploits in the wild.
Mitigation Recommendations
A fix is available in stigmem-node version 0.9.0a12. Users running multi-tenant deployments with the stigmem-plugin-multi-tenant should upgrade to version 0.9.0a12 or later to remediate this vulnerability. Patch status is not explicitly confirmed beyond the stated fix version; verify with the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-19T11:38:33.224Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a85bc7eacd9273b492f4a0c
Added to database: 08/19/2026, 14:23:58 UTC
Last enriched: 08/19/2026, 14:38:26 UTC
Last updated: 08/20/2026, 00:45:56 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.