CVE-2026-77320
TREK is a collaborative travel planner.
Does this matter?
Lower severity and a low EPSS score (0.29%). Track it; it rarely justifies an emergency change on its own.
Description
TREK is a collaborative travel planner. Prior to 3.3.0, getSharedTripData in server/src/services/shareService.ts returns days, assignments, dayNotes, and places through GET /api/shared/:token even when the trip owner disables share_map. The client hides the map, but the public JSON response still includes the itinerary and place names, coordinates, addresses, descriptions, notes, and prices. Anyone holding the valid share token can therefore read location and route information that the owner explicitly chose not to share, although the random token remains required and the flaw does not permit modification. This issue is fixed in version 3.3.0.
- CVSS 3.1
- 5.3 MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- 0.29% probability · 21th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-200, CWE-284, CWE-602
- Source
- security-advisories@github.com
EPSS moved from 0.2% on 25 September 2026 to 0.3% on 26 October 2026.
References
- https://github.com/liketrek/TREK/commit/19064b39176660f3be3a2df198c87949504046e2
- https://github.com/liketrek/TREK/pull/1520
- https://github.com/liketrek/TREK/releases/tag/v3.3.0
- https://github.com/liketrek/TREK/security/advisories/GHSA-9hc8-p7gm-p7mx
- https://github.com/liketrek/TREK/security/advisories/GHSA-9hc8-p7gm-p7mx
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.