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.
CVE-2026-76238
This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(medium)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity72% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026stigmem before 0.9.0a12 Cross-Tenant BOLA via decay sweep | Advisories | VulnCheck
https://www.vulncheck.com/advisories/stigmem-before-0a12-cross-tenant-bola-via-decay-sweepstigmem-node: decay sweep expires and counts facts across all tenants (cross-tenant BOLA) · Advisory · eidetic-labs/stigmem · GitHub
https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-6gqw-jqv7-v88mVendor Advisories for CVE-2026-76238(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 02:51 UTCEG score recompute
- 2026-08-21 02:51 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 14:43 UTCGHSA enrichment
- 2026-08-20 02:36 UTCGHSA enrichment
- 2026-08-19 14:26 UTCEG score recompute
- 2026-08-19 14:12 UTCEG score recompute
- 2026-08-19 14:12 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-76238?
When was CVE-2026-76238 disclosed?
Is CVE-2026-76238 actively exploited?
What is the CVSS score of CVE-2026-76238?
How do I remediate CVE-2026-76238?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76238
Is Your Infrastructure Affected by CVE-2026-76238?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.