Security readout for executives and security teams
Plain-English summary
Ech0 versions before 4.7.3 may leave stolen, non-expiring access tokens usable even after logout or administrative deletion. An attacker who already obtains such a token could retain authenticated access indefinitely, threatening confidential data and account integrity until the signing secret is rotated.
Executive priority
Treat this as an urgent identity-control issue. Prioritize internet-accessible or sensitive Ech0 deployments, upgrade promptly, and rotate signing secrets when theft cannot be excluded. The impact is potentially severe, although the sources provide no evidence of active exploitation.
Technical view
Three revocation paths fail for never-expire JWTs: logout can panic because ExpiresAt is nil, RevokeToken skips blacklisting when remaining TTL is zero, and administrative deletion omits the token JTI from the blacklist. Consequently, the signed token remains valid despite attempted revocation.
Likely exposure
Exposure is limited to Ech0 deployments before 4.7.3 using never-expire access tokens. Exploitation requires an attacker to first obtain a qualifying token. Risk is greatest where these tokens protect sensitive accounts or services and JWT secrets have not subsequently been rotated.
Exploitation context
The supplied record does not establish active exploitation and marks the CVE as absent from KEV. Exploitation depends on prior token theft, but successful compromise may provide persistent authenticated access because ordinary revocation actions fail.
Researcher notes
CWE-613 applies because session termination is ineffective for never-expire tokens. The CVSS 4.0 score is 9.1, with network reachability, high complexity, prerequisite conditions, and high confidentiality and integrity impact. The supplied evidence does not identify public exploitation or affected configurations beyond pre-4.7.3 deployments using never-expire tokens.
Mitigation direction
- Upgrade affected Ech0 deployments to version 4.7.3 or later.
- Follow the vendor advisory for any additional remediation requirements.
- Rotate the JWT signing secret if token theft is known or reasonably suspected.
- Review and restrict issuance of never-expire access tokens.
Validation and detection
- Inventory Ech0 versions and identify every deployment earlier than 4.7.3.
- Determine whether never-expire access tokens have been issued.
- Confirm upgraded deployments reject affected tokens after logout and administrative deletion.
- Review authentication records for unexpected reuse of supposedly revoked tokens.
- Verify JWT secret rotation invalidated previously issued tokens where compromise was suspected.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-613: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-79664 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.1CriticalVector: 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
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-fpw6-hrg5-q5x5)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Ech0 before 4.7.3 Access Token Revocation BypassCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
DEPRECATED: Insufficient Session Expiration
DEPRECATED: Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.