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

> Authenticated users can access other users' journey share tokens, leading to unauthorized disclosure of private travel data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-mx6m-qxv8-w624

## What is CVE-2026-54509?

CVE-2026-54509 is a medium-severity missing authorization vulnerability in mauriceboe TREK, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-54509?


## How do I fix CVE-2026-54509?

No fix has been published for CVE-2026-54509 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54509 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54509 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54509 and fix it if it is affected.

What it is: CVE-2026-54509 is a medium-severity missing authorization vulnerability in mauriceboe TREK, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54509 exists.

Affected product: mauriceboe TREK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54509/ (Markdown: https://insights.sbomify.com/CVE-2026-54509/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54509
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54509
- OSV: https://osv.dev/vulnerability/CVE-2026-54509

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54509/
Summaries are generated and may contain mistakes; the official description above is the record.