liketrek TREK up to 3.3.0 ssrfGuard ssrfGuard.ts checkSsrf server-side request forgery

Summaryinfo

A vulnerability identified as problematic has been detected in liketrek TREK up to 3.3.0. This affects the function checkSsrf of the file server/src/utils/ssrfGuard.ts of the component ssrfGuard. This manipulation causes server-side request forgery. This vulnerability is tracked as CVE-2026-85738. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in liketrek TREK up to 3.3.0 and classified as problematic. Affected by this vulnerability is the function checkSsrf of the file server/src/utils/ssrfGuard.ts of the component ssrfGuard. The manipulation with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality. The summary by CVE is:

TREK is a collaborative travel planner. Prior to 3.4.0, the checkSsrf logic in server/src/utils/ssrfGuard.ts does not recognize NAT64, 6to4, or Teredo IPv6 transition addresses that encode an IPv4 destination. An authenticated user who controls a DNS record can supply a URL whose AAAA result is a transition address embedding a private, loopback, or link-local IPv4 target, and isAlwaysBlocked and isPrivateNetwork classify the address as allowed. In a deployment that routes the applicable transition format, user-facing imports, webhooks, integrations, or plugin egress can reach internal services or cloud metadata and expose returned information. This issue is fixed in version 3.4.0.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-85738 since 09/04/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 3.4.0 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• liketrek

Name

• TREK

Version

• 3.0
• 3.1
• 3.2
• 3.3.0

Website

• Product: https://github.com/liketrek/TREK/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion