CVE-2026-76236

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 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 computed
Severity72% × 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, 2026
Patch available. Sources: github.
generic

stigmem before 0.9.0a12 Cross-Tenant BOLA via Tombstones | Advisories | VulnCheck

https://www.vulncheck.com/advisories/stigmem-before-0a12-cross-tenant-bola-via-tombstones
github Patch Available

stigmem-node: RTBF tombstones are mis-attributed and suppress reads tenant-blind (cross-tenant BOLA) · Advisory · eidetic-labs/stigmem · GitHub

https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-x26h-xmv8-gxf7

Vendor Advisories for CVE-2026-76236(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.

  1. 2026-08-20 23:24 UTCEG score recompute
  2. 2026-08-20 23:24 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 12:25 UTCGHSA enrichment
  5. 2026-08-20 01:26 UTCGHSA enrichment
  6. 2026-08-19 14:26 UTCEG score recompute
  7. 2026-08-19 14:12 UTCEG score recompute
  8. 2026-08-19 14:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76236?
CVE-2026-76236 is a high vulnerability published on August 19, 2026. 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. issuetombstone defaulted the tenant to "default" instead of the caller's tenant, allowing deletion records to be written to the wrong tenant,…
When was CVE-2026-76236 disclosed?
CVE-2026-76236 was first published in the National Vulnerability Database on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76236 actively exploited?
CVE-2026-76236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.4% of all scored CVEs.
What is the CVSS score of CVE-2026-76236?
CVE-2026-76236 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-76236?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76236, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-76236

Explore →

Is Your Infrastructure Affected by CVE-2026-76236?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs