CVE-2026-76242

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

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

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

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

stigmem Federation Peer Registration Authentication Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/stigmem-federation-peer-registration-authentication-bypass
github Patch Available

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 rangeFixed inDependents
stigmem-node0.9.0a10.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.

  1. 2026-08-21 05:28 UTCGHSA enrichment
  2. 2026-08-21 01:11 UTCEG score recompute
  3. 2026-08-21 01:11 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 20:55 UTCGHSA enrichment
  6. 2026-08-20 16:38 UTCEG score recompute
  7. 2026-08-20 16:38 UTCGHSA enrichment
  8. 2026-08-20 15:57 UTCEG score recompute
  9. 2026-08-20 15:57 UTCGHSA enrichment
  10. 2026-08-20 11:58 UTCGHSA enrichment
  11. 2026-08-20 07:36 UTCGHSA enrichment
  12. 2026-08-20 03:19 UTCGHSA enrichment
  13. 2026-08-19 23:00 UTCGHSA enrichment
  14. 2026-08-19 18:43 UTCGHSA enrichment
  15. 2026-08-19 14:26 UTCEG score recompute
  16. 2026-08-19 14:12 UTCEG score recompute
  17. 2026-08-19 14:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76242?
CVE-2026-76242 is a critical vulnerability 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 disclosed?
CVE-2026-76242 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76242 actively exploited?
CVE-2026-76242 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-76242?
CVE-2026-76242 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-76242?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76242, 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

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.