CVE-2026-76236

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-62476 (ENISA EUVD) · GHSA-77m3-9g4f-372v (GitHub Security Advisories)Source: ENISA EUVD

7.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.2HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity72% × 45%
Impact severity (EG Severity): CVSS 7.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.2): severity, escalated by confirmed exploitation. This CVE's 7.2 is its impact severity (EG Severity), not escalated.

EG Severity
7.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 19, 2026

Last Modified

September 11, 2026

Advisory Details (2)

Auto-updated Aug 19, 2026
Patch available. Sources: github.
Web page

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 advisoryMentions a patch (unverified)

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.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
stigmem-node0.9.0a1 ... 0.9.0a9 (11 versions)
  • every version up to 0.9.0a12: fixed in 0.9.0a12
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 55× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 228 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 128 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  3. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-10-27 17:30 UTCEG score recompute
  6. 2026-10-27 17:30 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-25 14:02 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-19 18:21 UTCEG score recompute
  17. 2026-10-19 18:20 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  20. 2026-10-18 03:13 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
Show 75 more
  1. 2026-10-13 07:10 UTCEG score recompute
  2. 2026-10-13 07:10 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  4. 2026-10-12 15:38 UTCEG score recompute
  5. 2026-10-11 19:24 UTCEG score recompute
  6. 2026-10-11 16:40 UTCEG score recompute
  7. 2026-10-11 13:59 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-08 08:36 UTCEG score recompute
  13. 2026-10-08 08:36 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-07 06:25 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  16. 2026-10-06 19:23 UTCEG score recompute
  17. 2026-10-06 19:23 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-06 08:00 UTCEG score recompute
  20. 2026-10-06 08:00 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  22. 2026-10-05 13:53 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  23. 2026-10-05 02:43 UTCEG score recompute
  24. 2026-10-05 02:43 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  26. 2026-10-04 15:43 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  27. 2026-10-04 04:07 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  28. 2026-10-03 16:58 UTCEG score recompute
  29. 2026-10-03 16:58 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  30. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  31. 2026-10-02 21:38 UTCEG score recompute
  32. 2026-10-02 21:38 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  33. 2026-10-02 09:47 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  34. 2026-10-01 22:48 UTCEG score recompute
  35. 2026-10-01 22:48 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  36. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  37. 2026-10-01 07:35 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  38. 2026-09-30 20:36 UTCEG score recompute
  39. 2026-09-30 20:36 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  40. 2026-09-30 08:50 UTCEG score recompute
  41. 2026-09-30 08:50 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  42. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  43. 2026-09-29 08:43 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  44. 2026-09-28 21:44 UTCEG score recompute
  45. 2026-09-28 21:44 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  46. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  47. 2026-09-28 05:02 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  48. 2026-09-27 18:03 UTCEG score recompute
  49. 2026-09-27 18:03 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  50. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  51. 2026-09-27 07:04 UTCEG score recompute
  52. 2026-09-27 07:04 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  53. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  54. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  55. 2026-09-25 06:48 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  56. 2026-09-24 19:48 UTCEG score recompute
  57. 2026-09-24 19:48 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  58. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  59. 2026-09-24 07:40 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  60. 2026-09-23 20:39 UTCEG score recompute
  61. 2026-09-23 20:39 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  62. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  63. 2026-09-23 09:40 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  64. 2026-09-22 22:40 UTCEG score recompute
  65. 2026-09-22 22:40 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  66. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  67. 2026-09-22 11:40 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  68. 2026-09-22 00:36 UTCEG score recompute
  69. 2026-09-22 00:36 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  70. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  71. 2026-09-21 13:37 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  72. 2026-09-21 02:36 UTCEG score recompute
  73. 2026-09-21 02:36 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH
  74. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  75. 2026-09-20 15:37 UTCGHSA enrichmentGHSA-77m3-9g4f-372v · GitHub severity HIGH

Frequently asked(5)

What is CVE-2026-76236?
CVE-2026-76236 is a high-severity vulnerability; its CVE record was 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. issue_tombstone 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 made public?
CVE-2026-76236 was made public on June 19, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 19, 2026. EchelonGraph's copy of the record carries a last-modified date of September 11, 2026; the record at its source may have been updated since.
Is CVE-2026-76236 actively exploited?
CVE-2026-76236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76236?
CVE-2026-76236 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76236?
A fix for CVE-2026-76236 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-76236 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.