Directory Traversal Affecting logto-1.39 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.54% (43rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-LOGTO139-19161590
  • published22 Aug 2026
  • disclosed19 Aug 2026

Introduced: 19 Aug 2026

CVE-2026-63188  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest logto-1.39.

NVD Description

Note: Versions mentioned in the description apply only to the upstream logto-1.39 package and not the logto-1.39 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 0.3.9, the Logto Tunnel npm package enabled createStaticFileProxy from packages/tunnel/src/commands/tunnel/index.ts and passed request.url from static asset requests through packages/tunnel/src/commands/tunnel/utils.ts using path.join(staticPath, request.url) and then fs.open(requestPath, "r") without URL normalization or a containment check. When --experience-path was enabled and the tunnel port was reachable, an unauthenticated requester could send a path containing ../ to createStaticFileProxy and read files outside the configured static directory that were readable by the logto-tunnel process. The service used server.listen(port), which could expose the tunnel to other hosts depending on the platform and deployment. This issue is fixed in version 0.3.9.