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.
CVE-2026-76242
This critical-severity CVE scores 9.1 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
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity91% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026stigmem Federation Peer Registration Authentication Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/stigmem-federation-peer-registration-authentication-bypassFederation 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-8fghVendor 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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| stigmem-node | 0.9.0a1 | 0.9.0a2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× 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 05:28 UTCGHSA enrichment
- 2026-08-21 01:11 UTCEG score recompute
- 2026-08-21 01:11 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 20:55 UTCGHSA enrichment
- 2026-08-20 16:38 UTCEG score recompute
- 2026-08-20 16:38 UTCGHSA enrichment
- 2026-08-20 15:57 UTCEG score recompute
- 2026-08-20 15:57 UTCGHSA enrichment
- 2026-08-20 11:58 UTCGHSA enrichment
- 2026-08-20 07:36 UTCGHSA enrichment
- 2026-08-20 03:19 UTCGHSA enrichment
- 2026-08-19 23:00 UTCGHSA enrichment
- 2026-08-19 18:43 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
Related CVEs(same CWE)
Same CWE
10 shownCWE-295
Frequently asked(5)
What is CVE-2026-76242?
When was CVE-2026-76242 disclosed?
Is CVE-2026-76242 actively exploited?
What is the CVSS score of CVE-2026-76242?
How do I remediate CVE-2026-76242?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-76242
Is Your Infrastructure Affected by CVE-2026-76242?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.