Unauthenticated account enumeration via login timing discrepancy
Published May 28, 2026 · Updated May 28, 2026
Observable timing discrepancy in TREK before 3.0.18 allows remote attackers to enumerate registered email addresses through login requests. POST /api/auth/login returns immediately for an unknown email but performs a slow bcrypt comparison for an existing account before returning the same 401 response. No authentication or user interaction is required, and the resulting account list supports targeted password and phishing attacks.
Summary
What happened
Observable timing discrepancy in TREK before 3.0.18 allows remote attackers to enumerate registered email addresses through login requests. POST /api/auth/login returns immediately for an unknown email but performs a slow bcrypt comparison for an existing account before returning the same 401 response. No authentication or user interaction is required, and the resulting account list supports targeted password and phishing attacks.
The record
- CVE
- CVE-2026-45410
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- Liketrek
- Product
- TREK
- Classifications
- CWE-203, CWE-208, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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.18
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.
Weakness, pattern, technique
Public exploit references
- TREK login timing enumeration proof of conceptproof of concept · demonstrated
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