Quick answers
- Is CVE-2026-54509 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54509 being exploited in the wild.
- How severe is CVE-2026-54509?
- Medium severity, with a CVSS score of 6.5, published 20 August 2026.
- Which products and versions are affected?
- TREK TREK 3.0.0 to 3.0.x.
- Is there a fix for CVE-2026-54509?
- A patch was published on 2026-06-16: Fix released in version 3.1.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54509 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-54509?
- Check whether anything you run is named in the advisory. 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
The GET /api/journeys/:id/share-link endpoint in server/src/routes/journey.ts fails to validate that the authenticated requester owns or has permission to access the targeted journey before returning its share token. An attacker can enumerate sequential journey IDs and request share links for any journey; the endpoint returns a valid share token without authorization checks. The token can then be used with the unauthenticated GET /api/public/journey/:token endpoint to retrieve journey entries, captions, locations, moods, gallery photos, photo paths, and asset identifiers. This is an insecure direct object reference (IDOR) vulnerability requiring only network access and valid authentication. The vulnerability was fixed in version 3.1.0 by adding proper authorization checks.
Affected products
- TREK TREK 3.0.0 to 3.0.x
Timeline
- 2026-08-20: disclosed: CVE-2026-54509 published on NVD
- 2026-06-16: patched: Fix released in version 3.1.0