TREK IDOR: any authenticated user can read another user's journey share token (full journey leak) (CVE-2026-54509) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-54509

TREK IDOR: any authenticated user can read another user's journey share token (full journey leak)

Answer in brief

CVE-2026-54509 records a Unknown severity vulnerability in TREK IDOR: any authenticated user can read another user's journey share token (full journey leak). The current sources do not mark it as known exploited. The current feed maps mauriceboe/TREK (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 20, 2026Updated Aug 20, 2026Source checked Aug 20, 2026First seen by HOL Aug 20, 2026Material review Aug 20, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps mauriceboe/TREK (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
mauriceboe/TREKgeneric	>= 3.0.0, < 3.1.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for mauriceboe/TREK.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 20, 2026

Sources and claim methodology

Upstream source description

TREK is a collaborative travel planner. From 3.0.0 until 3.1.0, the GET /api/journeys/:id/share-link route in server/src/routes/journey.ts returns the result of getJourneyShareLink() from server/src/services/journeyShareService.ts without checking whether the authenticated requester can access the journey. Any ordinary authenticated user can enumerate sequential journey IDs and retrieve tokens from journey_share_tokens for another user's journey. The token grants unauthenticated access through GET /api/public/journey/:token to the shared journey's entries, captions, locations, moods, gallery photos, photo paths, and asset identifiers. This issue is fixed in version 3.1.0.

Quoted source text, attributed separately from HOL analysis.