CVE-2026-54508Public exploitNetwork attack vector

Blind SSRF via unchecked redirect following

Published Aug 20, 2026 · Updated Aug 20, 2026

Server-side request forgery in TREK before 3.1.0 allows remote authenticated users to reach internal HTTP services via crafted redirector URLs. The importGoogleList(), importNaverList(), and resolveGoogleMapsUrl() sinks call checkSsrf() on only the initial URL and then use fetch() with redirect following, so each 30x Location hop is re-resolved without the DNS-pinned safeFetch path or any revalidation. Trip members can reach the list-import routes and any authenticated user can reach /api/maps/resolve-url; the result is blind GET-only access to loopback, RFC 1918, and cloud metadata endpoints, without response-body disclosure.

CVSS severity5.3
Medium
EPSS probability0.31%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Server-side request forgery in TREK before 3.1.0 allows remote authenticated users to reach internal HTTP services via crafted redirector URLs. The importGoogleList(), importNaverList(), and resolveGoogleMapsUrl() sinks call checkSsrf() on only the initial URL and then use fetch() with redirect following, so each 30x Location hop is re-resolved without the DNS-pinned safeFetch path or any revalidation. Trip members can reach the list-import routes and any authenticated user can reach /api/maps/resolve-url; the result is blind GET-only access to loopback, RFC 1918, and cloud metadata endpoints, without response-body disclosure.

The record

CVE
CVE-2026-54508
Published
Aug 20, 2026
Updated
Aug 20, 2026
Vendor
Liketrek
Product
TREK
Classifications
CWE-918, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 3.1.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Liketrek · TREKversion=< 3.1.0

Published CVSS scores

5.3GitHub, Inc.CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo