Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-77320 Overview
TREK is an open-source collaborative travel planner. CVE-2026-77320 is an information disclosure vulnerability [CWE-200] affecting all versions prior to 3.3.0. The getSharedTripData function in server/src/services/shareService.ts returns full itinerary data through the GET /api/shared/:token endpoint even when the trip owner has disabled the share_map option. While the client-side interface hides the map, the server still serves place names, coordinates, addresses, descriptions, notes, and prices in the JSON response. Any party holding the valid share token can read location and route data the owner explicitly chose not to expose. The flaw does not permit modification, and the random share token remains required for access.
Critical Impact
Holders of a shared trip token can retrieve detailed location data, including coordinates and addresses, that the trip owner disabled from sharing.
Affected Products
- TREK collaborative travel planner, all versions prior to 3.3.0
- server/src/services/shareService.tsgetSharedTripData function
- GET /api/shared/:token API endpoint
Discovery Timeline
- 2026-09-24 - CVE-2026-77320 published to the National Vulnerability Database (NVD)
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-77320
Vulnerability Analysis
The vulnerability is a server-side authorization enforcement gap. The TREK application allows trip owners to toggle a share_map preference that is intended to withhold map and location data from parties viewing a shared trip. The client application honors this preference by hiding the map component. However, the backend getSharedTripData service function in server/src/services/shareService.ts does not filter the response payload based on the share_map flag.
As a result, requests to GET /api/shared/:token return the complete trip object, including days, assignments, dayNotes, and places. The places array exposes names, coordinates, addresses, descriptions, notes, and prices. This matches the Common Weakness Enumeration pattern [CWE-200] for exposure of sensitive information to an unauthorized actor.
Root Cause
The root cause is reliance on client-side controls to enforce a privacy preference. The server trusts the client to render only non-restricted fields rather than filtering the response based on the owner's share_map setting. Authorization logic is incomplete because the share token grants access to the entire trip payload regardless of per-field privacy toggles.
Attack Vector
Exploitation requires a valid share token. A party already possessing the token can issue a direct HTTP request to GET /api/shared/:token using any HTTP client and parse the returned JSON. No authentication, user interaction, or elevated privileges are needed beyond possession of the token. The attack is strictly read-only; the issue does not allow modification of trip data.
See the GitHub Security Advisory GHSA-9hc8-p7gm-p7mx for additional technical context.
Detection Methods for CVE-2026-77320
Indicators of Compromise
- HTTP GET requests to the /api/shared/:token endpoint from unexpected IP addresses or user agents
- Response payloads from /api/shared/:token containing populated places, assignments, or dayNotes fields when the trip owner has disabled share_map
- Repeated enumeration-style access patterns against share token URLs
Detection Strategies
- Review web server and application logs for access to /api/shared/:token and correlate with the trip owner's share_map setting at request time
- Compare JSON response size against expected minimal payload size for trips with map sharing disabled
- Audit any downstream caches or content delivery networks (CDNs) that may have cached the full response
Monitoring Recommendations
- Log all requests to shared trip endpoints with full URL, source IP, and response byte count
- Alert on share token access from client fingerprints that do not match the TREK frontend
- Track share token access frequency per token to identify scraping behavior
How to Mitigate CVE-2026-77320
Immediate Actions Required
- Upgrade TREK to version 3.3.0 or later, which contains the server-side fix
- Rotate or invalidate existing share tokens for trips where share_map was disabled under the assumption that location data was private
- Notify trip owners who relied on the share_map toggle that previously issued tokens may have exposed location data
Patch Information
The fix is included in TREK release v3.3.0. The upstream change was merged via pull request #1520 and corresponds to commit 19064b3. Operators running self-hosted TREK deployments should pull the updated release and redeploy.
Workarounds
- Disable the shared trip feature entirely until upgrading to 3.3.0 by blocking the /api/shared/:token route at the reverse proxy
- Invalidate active share tokens in the database so previously distributed URLs stop resolving
- Place a web application firewall (WAF) rule in front of /api/shared/:token to strip restricted fields from JSON responses when the trip's share_map value is false
# Example nginx rule to block the shared endpoint until patched
location ~ ^/api/shared/ {
return 403;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

