Medium · CVSS 5.3CVE-2026-54508

TREK: Blind SSRF via unvalidated redirect-following in Google/Naver list import and Maps URL resolutionCVE-2026-54508

Answer in brief

CVE-2026-54508 records a Medium severity (CVSS 5.3) vulnerability in TREK: Blind SSRF via unvalidated redirect-following in Google/Naver list import and Maps URL resolution. The current sources do not mark it as known exploited. The current feed maps mauriceboe/TREK (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 20, 2026Updated Sep 18, 2026Source checked Oct 5, 2026First seen by HOL Aug 20, 2026Material review Sep 18, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps mauriceboe/TREK (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
mauriceboe/TREKgeneric	<3.1.0	3.1.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for mauriceboe/TREK.
Review the reported fix. Update mauriceboe/TREK to 3.1.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 20, 2026

Sources and claim methodology

Upstream source description

TREK is a collaborative travel planner. Prior to 3.1.0, TREK validates only the initial URL before native redirect following in importGoogleList() and importNaverList() in server/src/services/placeService.ts and resolveGoogleMapsUrl() in server/src/services/mapsService.ts. The affected sinks call checkSsrf() from server/src/utils/ssrfGuard.ts and then use fetch() with redirect: 'follow' instead of the DNS-pinned safeFetch() path, so a public attacker-controlled URL can redirect the server to loopback, RFC 1918, or cloud metadata addresses without revalidation. An authenticated trip member can reach the list-import routes, and any authenticated user can reach /api/maps/resolve-url, allowing blind GET requests to internal services without response-body reflection. This issue is fixed in version 3.1.0.

Quoted source text, attributed separately from HOL analysis.