Ech0 before 4.7.3 fails to properly revoke access tokens created with never-expire option, allowing attackers to maintain perpetual authenticated access after token theft. Three independent revocation mechanisms fail: logout panics on nil ExpiresAt field, RevokeToken skips when remainTTL is zero, and admin delete does not blacklist the JTI, leaving stolen tokens cryptographically valid until JWT secret rotation.
CVE-2026-79664
Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-25. a secondary CVSS source baseline 7.4; sources differ by 0.0.
- 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
- 7.4
- EG Score
- 7.4(high)
- EG Risk
- 49(Track*)EG Risk 49/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 computedSeverity74% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026Ech0 before 4.7.3 Access Token Revocation Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ech0-before-access-token-revocation-bypassAccess tokens with expiry=never cannot be revoked: logout panics, delete does not blacklist JTI · Advisory · lin-snow/Ech0 · GitHub
https://github.com/lin-snow/Ech0/security/advisories/GHSA-fpw6-hrg5-q5x5Vendor Advisories for CVE-2026-79664(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× 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-27 14:25 UTCEPSS rescore
- 2026-08-27 10:37 UTCGHSA enrichment
- 2026-08-26 23:19 UTCEG score recompute
- 2026-08-26 23:19 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 12:00 UTCGHSA enrichment
- 2026-08-26 00:41 UTCEG score recompute
- 2026-08-26 00:41 UTCGHSA enrichment
- 2026-08-25 13:22 UTCEG score recompute
- 2026-08-25 13:22 UTCGHSA enrichment
- 2026-08-25 13:16 UTCEG score recompute
- 2026-08-25 13:16 UTCGHSA enrichment
- 2026-08-25 12:17 UTCEG score recompute
- 2026-08-25 11:42 UTCEG score recompute
- 2026-08-25 11:41 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-613
Frequently asked(5)
What is CVE-2026-79664?
When was CVE-2026-79664 disclosed?
Is CVE-2026-79664 actively exploited?
What is the CVSS score of CVE-2026-79664?
How do I remediate CVE-2026-79664?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-79664
Is Your Infrastructure Affected by CVE-2026-79664?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.