CVE-2026-85738: TREK: SSRF Guard Bypass via IPv6 Transition Addresses (NAT64/6to4)

Published Sep 24, 2026
·
Updated

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.

Affected Software

1 affected component
TREK TREK<3.4.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade TREK to a version that resolves this vulnerability.

    Fixed in 3.4.0

Event History

Sep 24, 2026
CVE Published
via MITRE·06:09 PM
Data Sourced
via MITRE·06:09 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are practically exposed to this issue?

Deployments running TREK before 3.4.0 are exposed where a user-facing import, webhook, integration, or plugin can make outbound requests and the environment routes the relevant NAT64, 6to4, or Teredo address format. The impact can include access to internal services or cloud metadata and disclosure of returned information.

2

What does an attacker need to exploit the bypass?

The attacker needs an authenticated TREK account and control of a DNS record. They must cause the supplied URL to resolve through an AAAA record to a supported IPv6 transition address that embeds a private, loopback, or link-local IPv4 destination.

3

Are ordinary IPv6 destinations the issue?

No. The described bypass specifically relies on NAT64, 6to4, or Teredo IPv6 transition addresses that encode an IPv4 target and are incorrectly classified as allowed by the SSRF checks.

4

How can this be remediated?

Upgrade TREK to version 3.4.0, which fixes the issue. The provided data does not describe a separate workaround for deployments that cannot immediately upgrade.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203