CVE-2026-54508 TREK: Blind SSRF via unvalidated redirect-following in Google/Naver list import and Maps URL resolution
Authenticated users can trigger blind SSRF attacks against internal services via unvalidated redirects in URL import and resolution features.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-54508?
CVE-2026-54508 is a medium-severity server-side request forgery 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.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.
Weakness: CWE-918
Which versions are affected by CVE-2026-54508?
How do I fix CVE-2026-54508?
No fix has been published for CVE-2026-54508 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-54508 being exploited?
There is no known exploitation of CVE-2026-54508 in the wild and no public exploit code.
Sources
Also known as GHSA-f5vh-p2h5-x735.