MFA bypass via pre-2FA token replay
Published Aug 25, 2026 · Updated Aug 27, 2026
Improper authentication in Liketrek TREK 3.0.22 and earlier allows remote authenticated users to bypass MFA with a pre-2FA token. The login flow returns a purpose-scoped mfa_token after password verification, but the central JWT verifier ignores its purpose claim and treats it as a full session token. An attacker needs the victim's password and an MFA-enabled account at the default password version, then gains full account access without a TOTP or backup code.
Summary
What happened
Improper authentication in Liketrek TREK 3.0.22 and earlier allows remote authenticated users to bypass MFA with a pre-2FA token. The login flow returns a purpose-scoped mfa_token after password verification, but the central JWT verifier ignores its purpose claim and treats it as a full session token. An attacker needs the victim's password and an MFA-enabled account at the default password version, then gains full account access without a TOTP or backup code.
The record
- CVE
- CVE-2026-78863
- Published
- Aug 25, 2026
- Updated
- Aug 27, 2026
- Vendor
- Liketrek
- Product
- TREK
- Classifications
- CWE-287, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0
- Affected versionversion=3.0.1
- Affected versionversion=3.0.10
- Affected versionversion=3.0.11
- Affected versionversion=3.0.12
- Affected versionversion=3.0.13
- Affected versionversion=3.0.14
- Affected versionversion=3.0.15
- Affected versionversion=3.0.16
- Affected versionversion=3.0.17
- Affected versionversion=3.0.18
- Affected versionversion=3.0.19
- Affected versionversion=3.0.2
- Affected versionversion=3.0.20
- Affected versionversion=3.0.21
- Affected versionversion=3.0.22
- Affected versionversion=3.0.3
- Affected versionversion=3.0.4
- Affected versionversion=3.0.5
- Affected versionversion=3.0.6
- Affected versionversion=3.0.7
- Affected versionversion=3.0.8
- Affected versionversion=3.0.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo