TREK is a collaborative travel planner. Prior to 3.0.18, early return on missing user during login flow allowed an attacker to enumerate valid user accounts via response timing discrepancy. When an email address existed in the database, the backend performed a bcrypt password comparison before returning a 401 Unauthorized, adding ~370 ms of latency. When the email did not exist, the backend returned immediately (~10 ms). This ~14× timing difference could be detected without any difference in HTTP status codes or response bodies. This vulnerability is fixed in 3.0.18.
Metrics
Affected Vendors & Products
References
History
Fri, 29 May 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 29 May 2026 01:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mauriceboe
Mauriceboe trek |
|
| Vendors & Products |
Mauriceboe
Mauriceboe trek |
Thu, 28 May 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | TREK is a collaborative travel planner. Prior to 3.0.18, early return on missing user during login flow allowed an attacker to enumerate valid user accounts via response timing discrepancy. When an email address existed in the database, the backend performed a bcrypt password comparison before returning a 401 Unauthorized, adding ~370 ms of latency. When the email did not exist, the backend returned immediately (~10 ms). This ~14× timing difference could be detected without any difference in HTTP status codes or response bodies. This vulnerability is fixed in 3.0.18. | |
| Title | Time-based user enumeration in TREK authentication endpoint | |
| Weaknesses | CWE-203 CWE-208 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published: 2026-05-28T21:23:01.431Z
Updated: 2026-05-29T14:46:58.159Z
Reserved: 2026-05-12T01:48:40.452Z
Link: CVE-2026-45410
Updated: 2026-05-29T14:46:52.320Z
Status : Deferred
Published: 2026-05-28T22:17:01.050
Modified: 2026-05-29T16:32:14.400
Link: CVE-2026-45410
No data.