CVE-2026-76245

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% 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.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: 7.1Exploit: None knownExposed: 0

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

stigmem (pip package stigmem-node) version 0.9.0a1 contains a timestamp-handling mismatch in federation peer-token validation that can cause valid peer tokens to be incorrectly treated as expired. This affects the availability and reliability of authenticated federation flows on nodes using federation peer authentication paths. The issue is fixed in 0.9.0a2, which uses the canonical millisecond-based validation path.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
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 Token Timestamp Validation Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/stigmem-federation-peer-token-timestamp-validation-bypass
github Patch Available

Federation peer token timestamp validation may reject valid peer tokens · Advisory · eidetic-labs/stigmem · GitHub

Affected: 0.9.0a2. Federation peer-token timestamp handling now uses the canonical millisec

https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-xh5j-xjfq-qvvx

Vendor Advisories for CVE-2026-76245(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 12× in last 7d / 12× 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 03:57 UTCEG score recompute
  2. 2026-08-21 03:57 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 16:38 UTCEG score recompute
  5. 2026-08-20 16:38 UTCGHSA enrichment
  6. 2026-08-20 15:45 UTCEG score recompute
  7. 2026-08-20 15:45 UTCGHSA enrichment
  8. 2026-08-20 13:06 UTCGHSA enrichment
  9. 2026-08-20 01:46 UTCGHSA enrichment
  10. 2026-08-19 14:26 UTCEG score recompute
  11. 2026-08-19 14:12 UTCEG score recompute
  12. 2026-08-19 14:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76245?
CVE-2026-76245 is a high vulnerability published on August 19, 2026. stigmem (pip package stigmem-node) version 0.9.0a1 contains a timestamp-handling mismatch in federation peer-token validation that can cause valid peer tokens to be incorrectly treated as expired. This affects the availability and reliability of authenticated federation flows on nodes using…
When was CVE-2026-76245 disclosed?
CVE-2026-76245 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-76245 actively exploited?
CVE-2026-76245 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 91.8% of all scored CVEs.
What is the CVSS score of CVE-2026-76245?
CVE-2026-76245 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-76245?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76245, 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-76245

Explore →

Is Your Infrastructure Affected by CVE-2026-76245?

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

Start Free Scan →Browse All CVEs