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.
References
Configurations
No configuration.
History
29 May 2026, 16:16
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/mauriceboe/TREK/security/advisories/GHSA-3552-3c98-x79r - |
28 May 2026, 22:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-05-28 22:17
Updated : 2026-05-29 16:32
NVD link : CVE-2026-45410
Mitre link : CVE-2026-45410
CVE.ORG link : CVE-2026-45410
JSON object : View
Products Affected
No product.
