logto-io Logto up to 0.3.8 Tunnel index.ts createStaticFileProxy request.url path traversal

Summaryinfo

A vulnerability identified as problematic has been detected in logto-io Logto up to 0.3.8. This affects the function createStaticFileProxy of the file packages/tunnel/src/commands/tunnel/index.ts of the component Tunnel. The manipulation of the argument request.url leads to path traversal. This vulnerability is referenced as CVE-2026-63188. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in logto-io Logto up to 0.3.8 and classified as problematic. This issue affects the function createStaticFileProxy of the file packages/tunnel/src/commands/tunnel/index.ts of the component Tunnel. The manipulation of the argument request.url with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-63188 since 07/16/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

Upgrading to version 0.3.9 eliminates this vulnerability.

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

Productinfo

Vendor

• logto-io

Name

• Logto

Version

• 0.3.0
• 0.3.1
• 0.3.2
• 0.3.3
• 0.3.4
• 0.3.5
• 0.3.6
• 0.3.7
• 0.3.8

Website

• Product: https://github.com/logto-io/logto/

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