Is CVE-2026-45410 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-45410 being exploited in the wild.

How severe is CVE-2026-45410?

Medium severity, with a CVSS score of 5.3, published 28 May 2026.

Is there a fix for CVE-2026-45410?

A patch was published on 2026-05-28: Fix released in version 3.0.18 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-45410 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-45410?

Check whether you run Mauriceboe Trek at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-45410: mauriceboe TREK user enumeration via timing discrepancy in login flow

CVE-2026-45410 · Severity: medium · CVSS 5.3 · Published 2026-05-28

TREK, a collaborative travel planning application, is vulnerable to a flaw that allows outsiders to determine which email addresses are registered with the service. By measuring the time it takes for the login page to respond, an attacker can distinguish between valid and invalid accounts because the system processes real accounts more slowly. This information can be used to facilitate targeted phishing, password guessing attacks, or other unauthorized access attempts.

Technologies: Mauriceboe Trek. Vendors: Mauriceboe.

Quick answers

Is CVE-2026-45410 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-45410 being exploited in the wild.
How severe is CVE-2026-45410?: Medium severity, with a CVSS score of 5.3, published 28 May 2026.
Which products and versions are affected?: Mauriceboe Trek < 3.0.18.
Is there a fix for CVE-2026-45410?: A patch was published on 2026-05-28: Fix released in version 3.0.18 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-45410 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-45410?: Check whether you run Mauriceboe Trek at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A timing side-channel vulnerability exists in the POST /api/auth/login endpoint of TREK due to an observable timing discrepancy (CWE-208). The backend authentication handler returns an immediate response (~10ms) if a user email is not found in the database, but performs a computationally expensive bcrypt password comparison (~370ms) if the email exists. This ~14x difference in latency allows unauthenticated remote attackers to enumerate valid user accounts even when HTTP status codes and response bodies are identical (401 Unauthorized). The vulnerability is resolved in version 3.0.18 by ensuring consistent processing time regardless of user existence.

Affected products

mauriceboe TREK < 3.0.18

Timeline

2026-05-10: other: PoC created by researcher
2026-05-11: advisory: Vendor security advisory published
2026-05-28: disclosed: CVE published to NVD
2026-05-28: patched: Fix released in version 3.0.18

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.