CVE-2026-76238
Received Received - Intake

Broken Object Level Authorization in Stigmem Prior to 0.9.0a12

Vulnerability report for CVE-2026-76238, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-19

Last updated on: 2026-08-19

Assigner: VulnCheck

Description

stigmem versions before 0.9.0a12 contain a broken object level authorization vulnerability in the decay sweep endpoint that allows authenticated attackers with write credentials for one tenant to execute decay operations affecting all tenants. Attackers can submit POST requests to the decay sweep endpoint with ttl_seconds=0 to expire facts across all tenants, or use dry_run to obtain cross-tenant fact counts and existence information.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-19
Last Modified
2026-08-19
Generated
2026-08-19
AI Q&A
2026-08-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
stigmem stigmem to 0.9.0a12 (exc)
eidetic-labs stigmem to 0.9.0a12 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-76238 is a Broken Object Level Authorization (BOLA) vulnerability in stigmem versions before 0.9.0a12. It allows authenticated attackers with write credentials for one tenant to perform decay operations affecting all tenants. Attackers can submit POST requests to the decay sweep endpoint with ttl_seconds=0 to expire facts across all tenants or use dry_run to obtain cross-tenant fact counts and existence information.

Detection Guidance

To detect this vulnerability, check if your stigmem version is below 0.9.0a12. Run stigmem --version or inspect package metadata. Verify if multi-tenant mode is enabled by checking stigmem-plugin-multi-tenant configuration. Monitor API logs for POST requests to the decay sweep endpoint (/api/decay/sweep) with ttl_seconds=0 or dry_run=true from non-admin users.

Impact Analysis

This vulnerability can lead to data destruction affecting integrity and availability by expiring facts across all tenants. It also allows information disclosure by revealing cross-tenant fact counts and existence. The impact is limited to multi-tenant deployments; single-tenant setups are unaffected.

Compliance Impact

This vulnerability can violate compliance requirements by enabling unauthorized access to tenant data across all tenants, potentially breaching confidentiality and integrity. It may lead to data destruction or unauthorized information disclosure, which could result in non-compliance with GDPR, HIPAA, or other regulations.

Mitigation Strategies

Immediately upgrade stigmem to version 0.9.0a12 or later. Disable multi-tenant mode if not required. Restrict write credentials to the minimum necessary. Monitor for suspicious POST requests to the decay sweep endpoint. Apply network-level controls to limit access to the endpoint.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-76238. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart