Skip to main content
VulnerabilityPublished

CVE-2026-54509: mauriceboe TREK · Missing Authorization

Affects mauriceboe TREKSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.1.0 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.1.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade TREK and liketrek/TREK to 3.1.0.

Affected software

ProductAffectedFixed in
mauriceboeTREKAffected
  • >=3.0.0 <3.1.0
Fixed in
  • 3.1.0
GitHubliketrek/TREKpkg:github/liketrek/TREKOther threatsAffected
  • >=3.0.0 <3.1.0
Fixed in
  • 3.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade mauriceboe TREK to version 3.1.0 or later, where this authorization check issue is fixed. No other mitigations are indicated or required by the vendor advisory. Until patched, restrict access to authenticated users and monitor for unusual enumeration activity if possible.

Description

CVE-2026-54509 is a missing authorization vulnerability in mauriceboe TREK versions 3.0.0 up to but not including 3.1.0. The GET /api/journeys/:id/share-link endpoint does not verify if the authenticated user has permission to access the requested journey. This allows any authenticated user to enumerate journey IDs and obtain share tokens for other users' journeys. These tokens enable unauthenticated access to shared journey details such as entries, captions, locations, moods, gallery photos, photo paths, and asset identifiers. The issue is resolved in version 3.1.0.

References

Community reviews

Loading reviews…