---
id: "CVE-2026-63188"
kind: "vulnerability"
aliases: ["CVE-2026-63188", "GHSA-rxjr-6c9q-h67x"]
title: "logto-tunnel serves files outside `--experience-path` via path traversal"
severity: "high"
cvss: 8.7
epss: 0.0054
exploited: false
status: "open"
category: "package"
products: [{"name": "@logto/tunnel", "fixed": ["0.3.9"], "affected": "<= 0.3.8", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["cwe-22", "logto", "node", "npm", "package", "self-hosted"]
not_affected_if: ["no-experience-path", "tunnel-not-reachable", "version-0.3.9-or-later"]
published_at: "2026-08-19T20:17:20+00:00"
first_seen_at: "2026-11-05T17:38:59+00:00"
updated_at: "2026-11-05T17:40:05+00:00"
sources: [{"source": "ghsa", "url": "https://github.com/advisories/GHSA-rxjr-6c9q-h67x", "first_seen_at": "2026-11-05T17:38:59+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63188", "first_seen_at": "2026-11-05T17:40:05+00:00"}]
exploit_sources: [{"type": "epss", "score": 0.0054, "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-63188"}]
---

# logto-tunnel serves files outside `--experience-path` via path traversal

The @logto/tunnel npm package serves custom sign-in UI files from a local folder but does not stop '../' segments in request URLs. A network peer can request a path like /../secret.txt and read any file the logto-tunnel process can read.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- npm:@logto/tunnel affected <= 0.3.8 fixed 0.3.9

## How to check

- Check the installed version with `npm ls @logto/tunnel`; versions `0.3.8` and below are affected.
- Check whether the tunnel was started with `--experience-path` and whether its port is reachable from other hosts.

## Fix

- `@logto/tunnel` `0.3.9`

## Timeline

- 2026-11-05T17:38:59+00:00 ghsa https://github.com/advisories/GHSA-rxjr-6c9q-h67x
- 2026-11-05T17:40:05+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-63188

## Documents

- [advisory] Maintainer's advisory: api.github.com https://api.github.com/repos/logto-io/logto/security-advisories/GHSA-rxjr-6c9q-h67x
- [advisory] Maintainer's advisory: github.com https://github.com/logto-io/logto/security/advisories/GHSA-rxjr-6c9q-h67x
- [fix] Patch: github.com https://github.com/logto-io/logto/pull/9113
- [fix] Patch: github.com https://github.com/logto-io/logto/commit/5686815955534f803d3d50738259efd0f741e62c
- [fix] Release: github.com https://github.com/logto-io/logto/releases/tag/@logto/tunnel@0.3.9

## From the sources

### 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_