# CVE-2026-62945: TREK: Cross-trip reservation title disclosure via file links

> Authenticated users can leak private reservation titles from other trips by manipulating file link identifiers, exposing sensitive travel data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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-r4cp-666p-8f69

## What is CVE-2026-62945?

CVE-2026-62945 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. Prior to 3.1.3, TREK file upload, update, and link actions accept attacker-controlled reservation_id, place_id, and assignment_id values without using findForeignLinkTarget() to verify that the referenced object belongs to the file's trip. An authenticated user with file-edit permission on any accessible trip can submit a foreign reservation identifier through POST /api/trips/:tripId/files/:id/link, POST /api/trips/:tripId/files, or PUT /api/trips/:tripId/files/:id. Subsequent reads through FILE_SELECT or getFileLinks() join the foreign reservation and return reservation_title, disclosing reservation existence and titles across private trip boundaries. This issue is fixed in version 3.1.3.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-62945 being exploited?

There is no known exploitation of CVE-2026-62945 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62945 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: There is no known exploitation of CVE-2026-62945 in the wild and no public exploit code.

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-62945/ (Markdown: https://insights.sbomify.com/CVE-2026-62945/index.md)
```

## Sources

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

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