CVE-2026-79664

Ech0 before 4.7.3 Access Token Revocation Bypass

Published Aug 25, 2026 CVSS 4.0 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Ech0 versions earlier than 4.7.3 contain a flaw that prevents tokens issued with the never‑expire option from being properly invalidated. The application attempts to logout, revoke, or delete such tokens but the logic fails—logout triggers a panic when ExpiresAt is nil, the RevokeToken function skips tokens with a remaining TTL of zero, and an admin delete does not blacklist the token’s identifier. As a result, a stolen or guessed JWT remains cryptographically valid indefinitely, letting an attacker maintain authenticated access to the system after the token’s intended lifetime.

Affected Systems

The affected product is the Ech0 web platform from the vendor lin‑snow. Any deployment running Ech0 version 4.7.2 or earlier is vulnerable to this access‑token revocation bypass. No later releases are affected because the flaw was fixed in version 4.7.3.

Risk and Exploitability

The base CVSS score of 9.1 indicates a critical impact on confidentiality, integrity, and availability. The EPSS score is not available, so the current probability of exploitation cannot be quantified, and the vulnerability is not listed in CISA’s KEV catalog. However, an attacker who has obtained or guessed a valid JWT (through phishing, replay, or credential theft) can simply use that token forever, obviating the need for further exploitation. Once a token is stolen, it can be reused at will, providing a high‑value persistence vector that can be abused for prolonged clandestine access.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Ech0 to version 4.7.3 or later.
  • Rotate the JWT secret to invalidate all current tokens.
  • Monitor for abnormal login activity and confirm token revocation behaves correctly.

Generated by OpenCVE AI on August 25, 2026 at 12:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Lin-snow
Lin-snow ech0
Vendors & Products Lin-snow
Lin-snow ech0
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Ech0 before 4.7.3 Access Token Revocation Bypass
First Time appeared Ech0
Ech0 ech0
Weaknesses CWE-613
CPEs cpe:2.3:a:ech0:ech0:*:*:*:*:*:*:*:*
Vendors & Products Ech0
Ech0 ech0
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 9.1, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-613

    Insufficient Session Expiration

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 8, 2026, 3:25 PM
Reserved
Aug 25, 2026, 11:09 AM
Status
Awaiting Analysis
Published
Aug 25, 2026, 12:16 PM
Modified
Sep 23, 2026, 6:14 PM