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-77321 Overview
CVE-2026-77321 is an information disclosure vulnerability in TREK, a collaborative travel planner application. The flaw affects the Model Context Protocol (MCP) tool interface in versions prior to 3.3.0. The get_trip_summary tool in server/src/mcp/tools/trips.ts is registered for scoped OAuth MCP tokens without requiring the trips:read scope. A token issued only an unrelated capability, such as weather:read, can retrieve trip metadata, member email addresses, itinerary days, and accommodations for every trip accessible to the token's user. Cross-user authorization remains enforced, but the missing scope check breaks the consented least-privilege boundary. The issue is resolved in version 3.3.0.
Critical Impact
An MCP client holding a narrowly scoped OAuth token can read full trip summaries and third-party member email addresses it was never consented to access.
Affected Products
- TREK collaborative travel planner, all versions prior to 3.3.0
- TREK MCP server component (server/src/mcp/tools/trips.ts)
- TREK trip service exposing member data (server/src/services/tripService.ts)
Discovery Timeline
- 2026-09-24 - CVE-2026-77321 published to the National Vulnerability Database (NVD)
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-77321
Vulnerability Analysis
TREK exposes application functionality to AI assistants through an MCP server that validates OAuth 2.0 scopes on each registered tool. The get_trip_summary tool is registered without declaring the trips:read scope as a prerequisite. As a result, the MCP runtime permits any authenticated token to invoke the tool regardless of the capabilities the user granted during the OAuth consent flow.
Once invoked, the tool returns trip metadata, itinerary days, accommodations, and member email addresses pulled from server/src/services/tripService.ts. The response includes third-party contact information for every collaborator on each trip the token's user can access. This bypasses the consented least-privilege boundary that scoped tokens are intended to enforce [CWE-200]. Cross-user authorization is still applied, so a token cannot read trips belonging to other users.
Root Cause
The root cause is a missing scope declaration during MCP tool registration. The tool handler assumes the OAuth layer gates access, while the OAuth layer defers to per-tool scope metadata that was never defined. The resulting gap collapses the capability model from fine-grained scopes to coarse user-level authorization.
Attack Vector
An attacker who obtains an OAuth MCP token for an unrelated capability—for example, a weather integration granted only weather:read—can call get_trip_summary against the TREK MCP endpoint. The request succeeds and returns sensitive trip and collaborator data without additional prompts, consent dialogs, or privilege elevation.
// Patch excerpt - 3.3.0 (#1520), client/src/App.tsx
return (
- <div className="flex flex-col h-screen md:block md:h-auto">
+ <div className="flex flex-col h-dvh md:block md:h-auto">
<div className="flex-1 overflow-y-auto md:overflow-visible">{children}</div>
<BottomNav />
</div>
Source: GitHub Commit 19064b3. The authoritative server-side scope enforcement fix is described in GHSA-qvw8-w937-vcmq.
Detection Methods for CVE-2026-77321
Indicators of Compromise
- MCP tool invocations of get_trip_summary originating from OAuth tokens that were not granted trips:read.
- Access log entries showing successful responses from the trip summary endpoint to clients registered for unrelated scopes such as weather:read.
- Unusual read volume of trip metadata or member email fields by non-interactive MCP clients.
Detection Strategies
- Correlate OAuth token scope metadata with MCP tool call records to flag any get_trip_summary call lacking trips:read.
- Review MCP server audit logs for scope-mismatch patterns across all registered tools, not only trips.
- Compare pre- and post-upgrade behavior after deploying 3.3.0 to confirm scope rejection is now enforced.
Monitoring Recommendations
- Enable verbose logging on the MCP server for tool registration and per-call scope validation decisions.
- Alert on repeated 2xx responses to get_trip_summary from a single OAuth client in short windows.
- Track egress of member email addresses from tripService.ts to third-party MCP clients.
How to Mitigate CVE-2026-77321
Immediate Actions Required
- Upgrade TREK to version 3.3.0 or later, which adds the required trips:read scope check to get_trip_summary.
- Revoke and reissue existing OAuth MCP tokens so clients receive tokens scoped under the corrected policy.
- Audit prior MCP access logs for calls to get_trip_summary made by tokens without trips:read.
Patch Information
The fix is published in TREK release v3.3.0 via Pull Request #1520 and commit 19064b3. The advisory GHSA-qvw8-w937-vcmq documents the scope enforcement change in server/src/mcp/tools/trips.ts.
Workarounds
- Temporarily disable the get_trip_summary MCP tool registration until the upgrade is applied.
- Restrict OAuth client registration so only clients that legitimately require trips:read can obtain MCP tokens.
- Place the MCP server behind a reverse proxy that filters tool invocations based on externally mapped scope policies.
# Upgrade TREK to the patched release
git fetch --tags
git checkout v3.3.0
npm ci
npm run build
npm run start
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

