Vulnerability 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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://gist.github.com/jubnl/c2402adf85d946c1730867aeecc794de
- https://github.com/mauriceboe/TREK/security/advisories/GHSA-3552-3c98-x79r
- https://github.com/mauriceboe/TREK/security/advisories/GHSA-3552-3c98-x79r
FAQ
What is CVE-2026-45410?
CVE-2026-45410 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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 em...
How severe is CVE-2026-45410?
CVE-2026-45410 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-45410?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.