Path Traversal in @logto/tunnel (CVE-2026-63188)
Summary
Path traversal in @logto/tunnel (CVE-2026-63188). Risk of unauthorized operations or information disclosure. Exploitable via request.url. Mitigation: upgrade to 0.3.9 or later.
Original description
The description as published by the source.
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
- Create a custom UI directory at
/tmp/logto-ui/staticwith `/tm…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-63188 has been found in @logto/tunnel.
Attackers can target a specific entry point like request.url over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @logto/tunnel to 0.3.9 or later.
If unsure, ask your IT team or search "@logto/tunnel CVE-2026-63188" on the vendor's site.
CVE-2026-63188 (@logto/tunnel) — CWE-22
Attack surface: request.url / staticPath
Patched: 0.3.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in @logto/tunnel. Attackers reach the vulnerable code path via request.url.
Check the vendor advisory for the affected versions of @logto/tunnel. Attack surface: request.url / staticPath.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.3.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@logto/tunnel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@logto/tunnel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@logto/tunnelを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @logto/tunnel to 0.3.9ステージング環境で 0.3.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com