CVE-2026-76242

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (28th 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-62406 (ENISA EUVD) · GHSA-rgmr-4wwg-2c6j (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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.3%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

stigmem-node 0.9.0a1 accepts federation peer key material during peer registration without a separate administrator out-of-band fingerprint approval step. On nodes that accept federation peer registration over a network where initial registration can be intercepted or misdirected, an attacker can register a malicious peer and gain access to or tamper with federation traffic. Fixed in 0.9.0a2, which introduces a pending approval flow requiring administrator fingerprint verification before peer tokens are accepted.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.3%
EPSS %ILE
28th
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 Sep 15, 2026
Patch available. Sources: github.
Web page

stigmem Federation Peer Registration Authentication Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/stigmem-federation-peer-registration-authentication-bypass
GitHub advisoryMentions a patch (unverified)

Federation peer registration lacked explicit out-of-band approval · Advisory · eidetic-labs/stigmem · GitHub

Affected: 0.9.0a2. Peer registration now uses a pending approval flow, and peer tokens are

https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-9vp8-3hmv-8fgh

Vendor Advisories for CVE-2026-76242(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
  • every version up to 0.9.0a2: fixed in 0.9.0a2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 99× 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 401 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 301 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-76242?
CVE-2026-76242 is a critical-severity vulnerability; its CVE record was published on August 19, 2026. stigmem-node 0.9.0a1 accepts federation peer key material during peer registration without a separate administrator out-of-band fingerprint approval step. On nodes that accept federation peer registration over a network where initial registration can be intercepted or misdirected, an attacker can…
When was CVE-2026-76242 made public?
CVE-2026-76242 was made public on May 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-76242 actively exploited?
CVE-2026-76242 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76242?
CVE-2026-76242 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76242?
A fix for CVE-2026-76242 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-76242 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-76242

Explore →

Is Your Infrastructure Affected by CVE-2026-76242?

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

Book a Demo →Browse All CVEs