CVE-2026-63188: logto-tunnel serves files outside --experience-path via path traversal
Summary
@logto/tunnel serves custom sign-in experience files from the --experience-path directory. When the tunnel service is reachable, a requester can use ../ path segments in a static asset request to read files outside that directory that the CLI process can read.
Details
The tunnel command accepts --experience-path as the local folder path for custom sign-in experience assets. packages/tunnel/src/commands/tunnel/index.ts enables createStaticFileProxy(path) when that option is set and sends non-Logto, non---experience-uri requests to that static proxy. The server is started with server.listen(port).
packages/tunnel/src/commands/tunnel/utils.ts builds the filesystem path as path.join(staticPath, fallBackToIndex ? index : request.url). For file asset paths, request.url is used directly. A request URL such as /../secret.txt resolves outside staticPath and is then opened with fs.open(requestPath, 'r'). There is no URL normalization and no containment check that the resolved path remains under the configured static directory before the file is read and returned.
The proof boundary is the packaged CLI end-to-end run. The filesystem read primitive was validated with equivalent Node HTTP handling for the affected code path, including that Node preserves /../secret.txt in request.url and that bare server.listen(port) binds to all interfaces on this platform.
PoC
1. Create a custom UI directory at /tmp/logto-ui/static with /tmp/logto-ui/static/index.html. 2. Create a sibling file outside the static root, for example /tmp/logto-ui/secret.txt. 3. Start the tunnel with logto-tunnel --endpoint https://<tenant-id>.logto.app --port 9000 --experience-path /tmp/logto-ui/static. 4. Request http://<host>:9000/../secret.txt. 5. The response body contains the contents of /tmp/logto-ui/secret.txt.
Impact
The observed result is arbitrary file read outside the configured custom UI static directory. If the tunnel port is reachable from another host, an unauthenticated network peer can read local files readable by the logto-tunnel process, including development secrets or credentials stored near the custom UI project.
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@logto/tunnelto a version that resolves this vulnerability.Fixed in 0.3.9 - Upgrade
Upgrade
@logto/tunnelto a version that resolves this vulnerability.Fixed in 0.3.9
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments using Logto Tunnel versions before 0.3.9 with --experience-path enabled are affected. Exposure requires the tunnel port to be reachable; server.listen(port) may make it reachable from other hosts depending on the platform and deployment.
What does an attacker need to exploit the flaw?
An attacker only needs unauthenticated network access to the reachable tunnel port and must send a static-asset request containing ../ path traversal sequences. They can read files outside the configured static directory if those files are readable by the logto-tunnel process.
What is the remediation?
Upgrade the Logto Tunnel npm package to version 0.3.9 or later. The issue is fixed in 0.3.9.
What can be done if an upgrade cannot be applied immediately?
Disable use of --experience-path or prevent untrusted users and remote hosts from reaching the tunnel port. Restricting filesystem permissions for the logto-tunnel process also limits which files could be read.